🔼(deps): bump the github-actions group with 2 updates

[dependabot]

Bumps the github-actions group with 2 updates: provide-io/ci-tooling/.github/workflows/python-release.yml and astral-sh/setup-uv.

Updates provide-io/ci-tooling/.github/workflows/python-release.yml from 0.8.4 to 0.8.8

Changelog

Sourced from provide-io/ci-tooling/.github/workflows/python-release.yml's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Consumers pin this repository by tag or commit SHA, so a release changes nothing for a repository until that repository moves its uses: pin. Note that callers pin in two places: the uses: line and the ref: of the ci-tooling checkout used by the TestPyPI verification step.

[0.8.6] - 2026-09-06

Fixed

• Skipped test jobs no longer report their check name with the matrix expression un-interpolated.

  A job gated off by if: has no matrix context, so a name: referencing it was emitted verbatim: every consumer setting run-tests: false, or whose platform-preset excludes an architecture, showed rows reading 🧪 Tests (linux_amd64, py${{ matrix.python-version }}). Both states were visible in one run — provide-io/pyvider run 33991794320 rendered py3.11 on the five running legs and the raw expression on the one skipped.

  The names now carry only the platform. GitHub appends the matrix value to a static name on its own, single entry or several, so a running row still reads 🧪 Tests linux_amd64 (3.11) and a matrix-testing: true consumer keeps four distinguishable rows. Parentheses are left out of the platform because GitHub's suffix supplies them.

  Check names change for every consumer. Nothing is known to depend on them: all fourteen protected repositories require only ci / 📌 No Active Pins. A caller that lists a test job as a required status check must update that name.

[0.8.5] - 2026-09-05

Added

• ignore-vulnerabilities on python-ci.yml and python-security.yml, a comma-separated list of advisory IDs passed to pip-audit --ignore-vuln.

  A caller can hit an advisory whose fix it cannot take. terraform-provider-pyvider is the case this was written for: cryptography publishes no macOS x86_64 wheel from 49.0.0 on, so the darwin_amd64 package cannot be built above 48.0.1, and three advisories against 48.0.1 are fixed only in 49.0.0 and 50.0.0.

  Without this the choice is to turn fail-on-vulnerability off, which stops the audit gating anything at all. An entry here records that the project examined the finding and established it cannot reach the vulnerable code path; the reason belongs at the call site, beside the IDs. Everything not listed still fails the build, so a fourth advisory against the same package is caught.

Commits

• 16199c4 release: 0.8.8
• 5858c40 feat(release): refuse a release that carries less than the one before it (#43)
• b4b14ae docs(release): say what the PyPI gate actually buys (#41)
• 07f2a72 release: 0.8.7
• 42e988c feat(release): gate a release on the version being installable (#38)
• 96f836a release: 0.8.6
• ce6c3fa ci: keep skipped test rows readable by dropping matrix from job names (#37)
• 3bc4e6d release: 0.8.5
• ffc9d9c feat(security): let a caller accept an advisory it cannot fix
• See full diff in compare view

Updates astral-sh/setup-uv from 10.0.1 to 10.1.0

Release notes

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

v10.1.0 🌈 New output python-runtime-idand respect NO_PROXY

Changes

This release adds more bheind the scene security improvements and also 2 small improvements.

NO_PROXY

This action now respects no_proxy/NO_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 for details on why this can be useful.

🐛 Bug fixes

• fix: respect no proxy directive @​mj0nez (#1037)
• Use JSON + a typed wrapper instead of TS codegen @​woodruffw (#1025)

🚀 Enhancements

• Expose a Python "identity" output @​woodruffw (#1036)
• Verify downloads with astral-sh/versions checksums @​zaniebot (#1033)

🧰 Maintenance

• chore: update known checksums for 0.12.12 @github-actions[bot] (#1041)
• chore: update known checksums for 0.12.10/0.12.11 @github-actions[bot] (#1038)
• chore: update known checksums for 0.12.9 @github-actions[bot] (#1035)
• chore: update known checksums for 0.12.7/0.12.8 @github-actions[bot] (#1031)
• chore: update known checksums for 0.12.6 @github-actions[bot] (#1030)
• chore: update known checksums for 0.12.5 @github-actions[bot] (#1020)
• Use self-repo syntax for all in-repo actions/reusable workflows @​woodruffw (#1024)
• Pin one-shot tools @​woodruffw (#1022)
• ci: remove obsolete direct push attempts @​eifinger (#1019)

📚 Documentation

• docs: update version references to v10.0.1 @github-actions[bot] (#1018)

⬆️ Dependency updates

• chore(deps-dev): roll up Dependabot updates @​eifinger (#1043)
• Harden npm install defaults @​zaniebot (#1026)
• Add dependency cooldowns @​woodruffw (#1021)

Commits

• bec219d chore(deps-dev): roll up Dependabot updates (#1043)
• b90ec40 fix: respect no proxy directive (#1037)
• 421feb6 chore: update known checksums for 0.12.12 (#1041)
• f634bf4 Expose a Python "identity" output (#1036)
• a6772c8 chore: update known checksums for 0.12.10/0.12.11 (#1038)
• e105c8f chore: update known checksums for 0.12.9 (#1035)
• cd13f92 Verify downloads with astral-sh/versions checksums (#1033)
• 3aef7b9 chore: update known checksums for 0.12.7/0.12.8 (#1031)
• d08d816 chore: update known checksums for 0.12.6 (#1030)
• 19b4d1e Harden npm install defaults (#1026)
• 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 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