Skip to content

ci(deps): update github-actions (major) - #534

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-github-actions
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-github-actions

Conversation

@renovate

@renovate renovate Bot commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v9.0.0 → v10.4.0
node uses-with major 24 → 26

Release Notes

astral-sh/setup-uv

v10.4.0: 🌈 New input require-checksums and bug fixing

Compare Source

Changes

This release adds the new input require-checksums. Its false by default and when you enable it, it will fail the action when no checksum is known for a release. This can happen when you use version: latest and the version of astral-sh/setup-uv that you are running does not bundle the known checksum for the uv version just released. In that case you can always supply the checksum yourself using the checksum input.

It is also a second layer of defense when using version: latest-known


Special thanks to @​yamamoto7 that fixed using PEP440 specifiers in the version and @​zsol for fixing cache-python: true on Windows runners.

🐛 Bug fixes

🚀 Enhancements

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

v10.3.3: 🌈 Use Astral mirror for version manifests with GitHub fallback

Compare Source

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable.
(Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes

🧰 Maintenance

📚 Documentation

v10.3.2: 🌈 update known checksums for 0.13.5

Compare Source

Changes

🧰 Maintenance

📚 Documentation

v10.3.1: 🌈 preserve cache error class names in save-cache bundle

Compare Source

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v10.3.0: 🌈 Add Python architecture selection

Compare Source

Changes

This release adds the python-arch input to select a Python architecture independently of the Python version. With uv 0.13.0 or later, set python-arch: x86_64 to use x64 Python on Windows ARM64 runners.

It also includes embedded checksums for uv releases through 0.13.0.

🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates

v10.2.0: 🌈 Disable automatic cache saves for merge queues

Compare Source

Changes

This release contains the known-checksum of the most recent uv releases and also disabled the uploading(saving) of the cache when in a merge queue since theses caches would almost never be used.

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

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

Compare Source

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 (comment) for details on why this can be useful.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v10.0.1: 🌈 Tolerate transient manifest timeouts

Compare Source

Changes

Thank you @​arguile- for making this action more resilient.

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

v10.0.0: 🌈 Disable automatic caching for sensitive events and new QOL features

Compare Source

Changes

Another breaking release, directly after v9.0.0 but we think the added security justifies that.

Extra security by default

If you use the default enable-cache: auto this will now DISABLE THE CACHE to protect against cache poisoning for the following events:

  • pull_request_target
  • workflow_run
  • release

You can read the full reasoning in #​984

version: latest-known
- name: Install the latest version of uv known to setup-uv
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version: "latest-known"

This will now install the latest version with a checksum that is known by this action. The known uv checksums are automatically updated but will take a release of this action to take effect. You won't be always using the latest & greatest but you will have an extra level of security.

Read python version from .tool-versions
- name: Install uv based on the version defined in .tool-versions and also set python
  uses: astral-sh/setup-uv@v10.0.0
  with:
    version-file: "pyproject.toml"

Will now also set the python version if it is defined in .tool-versions. You can read the details in the docs

🚨 Breaking changes
🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
actions/node-versions (node)

v26.13.1: 26.13.1

Compare Source

Node.js 26.13.1

v26.13.0: 26.13.0

Compare Source

Node.js 26.13.0

v26.12.1: 26.12.1

Compare Source

Node.js 26.12.1

v26.12.0: 26.12.0

Compare Source

Node.js 26.12.0

v26.11.1: 26.11.1

Compare Source

Node.js 26.11.1

v26.11.0: 26.11.0

Compare Source

Node.js 26.11.0

v26.10.0: 26.10.0

Compare Source

Node.js 26.10.0

v26.9.0: 26.9.0

Compare Source

Node.js 26.9.0

v26.8.2: 26.8.2

Compare Source

Node.js 26.8.2

v26.8.1: 26.8.1

Compare Source

Node.js 26.8.1

v26.8.0: 26.8.0

Compare Source

Node.js 26.8.0

v26.7.0: 26.7.0

Compare Source

Node.js 26.7.0

v26.6.0: 26.6.0

Compare Source

Node.js 26.6.0

v26.5.1: 26.5.1

Compare Source

Node.js 26.5.1

v26.5.0: 26.5.0

Compare Source

Node.js 26.5.0

v26.4.0: 26.4.0

Compare Source

Node.js 26.4.0

v26.3.1: 26.3.1

Compare Source

Node.js 26.3.1

v26.3.0: 26.3.0

Compare Source

Node.js 26.3.0

v26.2.0: 26.2.0

Compare Source

Node.js 26.2.0

v26.1.0: 26.1.0

Compare Source

Node.js 26.1.0

v26.0.0: 26.0.0

Compare Source

Node.js 26.0.0


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • "before 6am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 2 times, most recently from a1010db to cde6706 Compare August 30, 2026 21:57
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 2 times, most recently from 7c00ea0 to 78b78e2 Compare September 7, 2026 22:03
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 4 times, most recently from 169ef7f to 33a3a47 Compare September 16, 2026 19:12
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 2 times, most recently from 2ad9343 to e370ccc Compare September 24, 2026 18:12
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch from e370ccc to f58cf1a Compare September 30, 2026 19:29
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 3 times, most recently from f471228 to f342537 Compare October 15, 2026 17:01
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 5 times, most recently from bbb3eb3 to a31a528 Compare October 27, 2026 01:37
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 2 times, most recently from 36bfecf to a7e2a99 Compare October 28, 2026 00:33
@renovate renovate Bot changed the title ci(deps): update astral-sh/setup-uv action to v10 ci(deps): update github-actions (major) Oct 28, 2026
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 3 times, most recently from 0d66df5 to fad5976 Compare October 29, 2026 04:25
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch 3 times, most recently from 6d4c5a8 to 8a6a67f Compare November 12, 2026 03:34
@renovate
renovate Bot force-pushed the renovate/major-github-actions branch from 8a6a67f to 55757a7 Compare November 20, 2026 14:58
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants