scikit_build_example icon indicating copy to clipboard operation
scikit_build_example copied to clipboard
verified publisher icon pybind

chore(deps): bump the actions group across 1 directory with 4 updates

Open dependabot[bot] opened this issue 10 months ago • 0 comments

Bumps the actions group with 4 updates in the / directory: conda-incubator/setup-miniconda, pypa/cibuildwheel, astral-sh/setup-uv and actions/attest-build-provenance.

Updates conda-incubator/setup-miniconda from 3.1.0 to 3.1.1

Release notes

Sourced from conda-incubator/setup-miniconda's releases.

Version 3.1.1

Fixes

  • #378: Make nodefaults warning more explicit
  • #387: Detect and support Linux ARM runners for both Miniconda and Miniforge

Tasks and Maintenance

  • #374: Bump conda-incubator/setup-miniconda from 3.0.4 to 3.1.0
  • #375: Bump actions/cache from 3 to 4
  • #384: Bump @​actions/tool-cache from 2.0.1 to 2.0.2
  • #386: Fix link to example 14
  • #388: Fix mamba 1.x examples

#374: conda-incubator/setup-miniconda#374 #375: conda-incubator/setup-miniconda#375 #378: conda-incubator/setup-miniconda#378 #384: conda-incubator/setup-miniconda#384 #386: conda-incubator/setup-miniconda#386 #387: conda-incubator/setup-miniconda#387 #388: conda-incubator/setup-miniconda#388

Changelog

Sourced from conda-incubator/setup-miniconda's changelog.

v3.1.1 (2025-01-20)

Fixes

  • #378: Make nodefaults warning more explicit
  • #387: Detect and support Linux ARM runners for both Miniconda and Miniforge

Tasks and Maintenance

  • #374: Bump conda-incubator/setup-miniconda from 3.0.4 to 3.1.0
  • #375: Bump actions/cache from 3 to 4
  • #384: Bump @​actions/tool-cache from 2.0.1 to 2.0.2
  • #386: Fix link to example 14
  • #388: Fix mamba 1.x examples

#374: conda-incubator/setup-miniconda#374 #375: conda-incubator/setup-miniconda#375 #378: conda-incubator/setup-miniconda#378 #384: conda-incubator/setup-miniconda#384 #386: conda-incubator/setup-miniconda#386 #387: conda-incubator/setup-miniconda#387 #388: conda-incubator/setup-miniconda#388

Commits

Updates pypa/cibuildwheel from 2.22 to 2.23

Release notes

Sourced from pypa/cibuildwheel's releases.

v2.23.0

  • ✨ Adds official support for the new GitHub Actions Arm runners. In fact these worked out-of-the-box, now we include them in our tests and example configs. (#2135 via #2281)
  • ✨ Adds support for building PyPy 3.11 wheels (#2268 via #2281)
  • 🛠 Adopts the beta pypa/manylinux image for armv7l builds (#2269 via #2281)
  • 🛠 Dependency updates, including Pyodide 0.27 (#2117 and #2281)
Changelog

Sourced from pypa/cibuildwheel's changelog.

title: Changelog

Changelog

v2.23.0

1 March 2025

  • ✨ Adds official support for the new GitHub Actions Arm runners. In fact these worked out-of-the-box, now we include them in our tests and example configs. (#2135 via #2281)
  • ✨ Adds support for building PyPy 3.11 wheels (#2268 via #2281)
  • 🛠 Adopts the beta pypa/manylinux image for armv7l builds (#2269 via #2281)
  • 🛠 Dependency updates, including Pyodide 0.27 (#2117 and #2281)

v2.22.0

23 November 2024

  • 🌟 Added a new CIBW_ENABLE/enable feature that replaces CIBW_FREETHREADED_SUPPORT/free-threaded-support and CIBW_PRERELEASE_PYTHONS with a system that supports both. In cibuildwheel 3, this will also include a PyPy setting and the deprecated options will be removed. (#2048)
  • 🌟 Dependency groups are now supported for tests. Use CIBW_TEST_GROUPS/test-groups to specify groups in [dependency-groups] for testing. (#2063)
  • 🌟 Support for the experimental Ubuntu-based ARMv7l manylinux image (#2052)
  • ✨ Show a warning when cibuildwheel is run from Python 3.10 or older; cibuildwheel 3.0 will require Python 3.11 or newer as host (#2050)
  • 🐛 Fix issue with stderr interfering with checking the docker version (#2074)
  • 🛠 Python 3.9 is now used in CIBW_BEFORE_ALL/before-all on linux, replacing 3.8, which is now EoL (#2043)
  • 🛠 Error messages for producing a pure-Python wheel are slightly more informative (#2044)
  • 🛠 Better error when uname -m fails on ARM (#2049)
  • 🛠 Better error when repair fails and docs for abi3audit on Windows (#2058)
  • 🛠 Better error when manylinux-interpreters ensure fails (#2066)
  • 🛠 Update Pyodide to 0.26.4, and adapt to the unbundled pyodide-build (now 0.29) (#2090)
  • 🛠 Now cibuildwheel uses dependency-groups for development dependencies (#2064, #2085)
  • 📚 Docs updates and tidy ups (#2061, #2067, #2072)

v2.21.3

9 October 2024

  • 🛠 Update CPython 3.13 to 3.13.0 final release (#2032)
  • 📚 Docs updates and tidy ups (#2035)

v2.21.2

2 October 2024

  • ✨ Adds support for building 32-bit armv7l wheels on musllinux. On a Linux system with emulation set up, set CIBW_ARCHS to armv7l on Linux to try it out if you're interested! (#2017)
  • 🐛 Fix Linux Podman builds on some systems (#2016)
  • ✨ Adds official support for running on Python 3.13 (#2026)
  • 🛠 Update CPython 3.13 to 3.13.0rc3 (#2029)

... (truncated)

Commits

Updates astral-sh/setup-uv from 4 to 5

Release notes

Sourced from astral-sh/setup-uv's releases.

v5.2.1 🌈 Support toml spec 1.0.0

v5.2.0 introduced TOML parsing using @​iarna/toml because we already found out in astral-sh/ruff-action that toml has missing features.

As it turns out @​iarna/toml also is not fully TOML spec (1.0.0) compliant.

We now use smol-toml

🐛 Bug fixes

v5.0.0 🎄 Merry Christmas - Help fastly and users by default

Changes

This christmans 🎄 release is a bit early bit still full of presents 🎁 Since we are changing some of the defaults this can lead to breaking changes, thus the major version increase.

Here are the highlights:

Default to enable-cache: true on GitHub hosted runners

Did you know that that Fastly, the company hosting PyPI, theoretically has to pay $12.5 million per month and so far have served more than 2.41 exabytes of data? image

This is why they asked us to turn on caching by default. After weighting the pros and cons we decided to automatically upload the cache to the GitHub Actions cache when running on GitHub hosted runners. You can still disable that with enable-cache: false.

I remember when I first got into actions and didn't understand all the magic. I was baffled that some actions did something behind the scenes to make everything faster. I hope with this change we help a lot of users who are don't want to or are afraid to understand what enable-cache does.

Add **/requirements*.txt to default cache-dependency-glob

If caching is enabled we automatically searched for a uv.lock file and when this changed we knew we had to refresh the cache. A lot of projects don't use this but rather the good old requirements.txt. We now automatically search for both uv.lockand requirements*.txt (this means also requirements-test.txt, requirements-dev.txt, ...) files. You can change this with cache-dependency-glob

Auto activate venv when python-version is set

Some workflows install packages on the fly. This automatically works when using a python version that is already present on the runner. But if uv installs the version, e.g. because it is a free-threaded version or an old one, it is a standalone-build and installing packages "into the system" is not possible.

We now automatically create a new virtual environment with uv venv and activate it for the rest of the workflow if python-version is used. This means you can now do

- name: Install uv
  uses: astral-sh/setup-uv@auto-environment
  with:
    python-version: 3.13t
- run: uv pip install -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple cython

🚨 Breaking changes

... (truncated)

Commits

Updates actions/attest-build-provenance from 1 to 2

Release notes

Sourced from actions/attest-build-provenance's releases.

v2.0.0

The attest-build-provenance action now supports attesting multiple subjects simultaneously. When identifying multiple subjects with the subject-path input a single attestation is created with references to each of the supplied subjects, rather than generating separate attestations for each artifact. This reduces the number of attestations that you need to create and manage.

What's Changed

Full Changelog: https://github.com/actions/attest-build-provenance/compare/v1.4.4...v2.0.0

v1.4.4

What's Changed

Full Changelog: https://github.com/actions/attest-build-provenance/compare/v1.4.3...v1.4.4

v1.4.3

What's Changed

Full Changelog: https://github.com/actions/attest-build-provenance/compare/v1.4.2...v1.4.3

v1.4.2

What's Changed

Full Changelog: https://github.com/actions/attest-build-provenance/compare/v1.4.1...v1.4.2

v1.4.1

What's Changed

Full Changelog: https://github.com/actions/attest-build-provenance/compare/v1.4.0...v1.4.1

v1.4.0

What's Changed

... (truncated)

Commits
  • bd77c07 bump predicate from 1.1.4 to 1.1.5 (#485)
  • 1176ef5 bump @​actions/attest from 1.5.0 to 1.6.0 (#484)
  • f9eaf23 Bump actions/attest from 2.2.0 to 2.2.1 (#481)
  • f1321ec Bump @​octokit/request from 8.2.0 to 8.4.1 (#478)
  • d8181f5 Bump the npm-development group with 6 updates (#476)
  • 1f22f30 Bump @​octokit/request-error from 5.0.1 to 5.1.1 (#469)
  • 6e5e68c Bump the npm-development group with 4 updates (#471)
  • 555f5b7 Bump the npm-development group with 6 updates (#465)
  • 2d4fa84 Bump the npm-development group with 2 updates (#461)
  • ccf3390 Bump undici from 5.28.4 to 5.28.5 (#457)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

dependabot[bot] avatar Mar 03 '25 05:03 dependabot[bot]