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

[dependabot]

Bumps the actions group with 3 updates in the / directory: conda-incubator/setup-miniconda, 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

• 505e639 Prepare 3.1.1 (#389)
• ee41d4f Bump @​actions/tool-cache from 2.0.1 to 2.0.2 (#384)
• 7611e53 Detect and support Linux ARM runners for both Miniconda and Miniforge (#387)
• 254deea Merge pull request #388 from conda-incubator/mamba-1x
• 2ea4cd7 Do not test mambaforge
• 1a1de20 husky
• 6902f23 fix link
• 6bb0a7d revert workarounds for 2024's conda-libmamba-solver
• 47a6dcf Unpin mamba
• eacf539 Fix link to example 14. (#386)
• Additional commits viewable in compare view

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

• Support toml spec 1.0.0 @​eifinger (#245)

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?

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

• Default to enable-cache: true on GitHub hosted runners @​eifinger (#193)

... (truncated)

Commits

• b5f58b2 Support toml spec 1.0.0 (#245)
• 4e3dbec Add venv/bin as absolute path to PATH (#241)
• 2487ffc Bump @​octokit/rest from 21.0.2 to 21.1.0 (#229)
• 118b721 chore: update known checksums for 0.5.20 (#238)
• d942048 chore: update known checksums for 0.5.19 (#237)
• 77cc1ae Bump typescript from 5.7.2 to 5.7.3 (#230)
• 169ed2a Bump @​types/node from 22.10.5 to 22.10.6 (#236)
• 9fffe05 Add documentation for new inputs uv-file and pyproject-file (#235)
• 5ce9ee0 Detect required-version from config file (#233)
• d577e74 chore: update known checksums for 0.5.18 (#232)
• Additional commits viewable in compare view

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

• Bump cross-spawn from 7.0.3 to 7.0.6 by @​dependabot in actions/attest-build-provenance#319
• Prepare v2.0.0 release by @​bdehamer in actions/attest-build-provenance#321
  • Bump actions/attest from 1.4.1 to 2.0.0 (w/ multi-subject attestation support)

Full Changelog: actions/attest-build-provenance@v1.4.4...v2.0.0

v1.4.4

What's Changed

• Bump predicate action from 1.1.3 to 1.1.4 by @​bdehamer in actions/attest-build-provenance#310
  • Bump @​actions/core from 1.10.1 to 1.11.1 by @​dependabot in actions/attest-build-provenance#275
  • Bump @​actions/attest from 1.4.2 to 1.5.0 by @​bdehamer in actions/attest-build-provenance#309
    • Fix SLSA provenance bug related to workflow_ref OIDC token claims containing the "@" symbol in the tag name (actions/toolkit#1863)

Full Changelog: actions/attest-build-provenance@v1.4.3...v1.4.4

v1.4.3

What's Changed

• Bump predicate from 1.1.2 to 1.1.3 by @​bdehamer in actions/attest-build-provenance#226
  • Bump @​actions/attest from 1.3.1 to 1.4.1 by @​dependabot in actions/attest-build-provenance#212
  • Bump @​actions/attest from 1.4.1 to 1.4.2 by @​bdehamer in actions/attest-build-provenance#225
  • Fix bug w/ customized OIDC issuer URL for enterprise accounts (#222)

Full Changelog: actions/attest-build-provenance@v1.4.2...v1.4.3

v1.4.2

What's Changed

• Bump actions/attest from 1.4.0 to 1.4.1 by @​bdehamer in actions/attest-build-provenance#209
  • Includes bug fix for issue with authenticated proxies (actions/toolkit#1798)

Full Changelog: actions/attest-build-provenance@v1.4.1...v1.4.2

v1.4.1

What's Changed

• Update predicate action to 1.1.2 by @​bdehamer in actions/attest-build-provenance#197
  • Dynamic construction of oidc issuer by @​bdehamer in actions/attest-build-provenance#195

Full Changelog: actions/attest-build-provenance@v1.4.0...v1.4.1

v1.4.0

What's Changed

• Bump predicate action from 1.1.0 to 1.1.1 by @​bdehamer in actions/attest-build-provenance#182
  • Fix for JWKS proxy bug
• Bump actions/attest from 1.3.3 to 1.4.0 by @​bdehamer in actions/attest-build-provenance#183

... (truncated)

Commits

• 520d128 bump actions/attest from v2.1.0 to v2.2.0 (#449)
• 5d2ced9 Add example of upload-artifaction integration (#450)
• 3c016c1 bump actions/attest from v2.1.0 to v2.2.0 (#449)
• e06bbaf Bump the npm-development group with 3 updates (#447)
• 47c6e87 Bump the npm-development group with 4 updates (#444)
• c083b46 Bump the npm-development group with 2 updates (#438)
• 1b4b366 Bump typescript-eslint in the npm-development group (#434)
• 963f8a0 Bump the npm-development group with 2 updates (#429)
• 4ecada3 Bump the npm-development group across 1 directory with 3 updates (#422)
• f4b7552 bump eslint from 8.57.1 to 9.16.0 (#418)
• 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]

Looks like these dependencies are updatable in another way, so this is no longer needed.