Skip to content

chore(deps): update astral-sh/setup-uv action to v10 - #37

Open
kognic-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/astral-sh-setup-uv-10.x
Open

chore(deps): update astral-sh/setup-uv action to v10#37
kognic-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/astral-sh-setup-uv-10.x

Conversation

@kognic-renovate

@kognic-renovate kognic-renovate Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action major v8.3.2v10.0.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

astral-sh/setup-uv (astral-sh/setup-uv)

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

v9.0.0: 🌈 Change prune-cache default to false

Compare Source

Changes

This release disables the default cache cache pruning to ease the load on the PyPi infrastructure.
Since users might experience more GitHub Actions cache usage which might result in higher costs this is marked as a breaking change. To read more on why we did this (now) you can read the detailed analysis and reasoning in #​967

Besides this big breaking change we also have a small bugfix while building caches for linux distributions that behave a big different than the "big ones" and a speed up in version resolution by only reading the version manifest until a matching version is found saving runtime and network bandwith.

🚨 Breaking changes

🐛 Bug fixes

  • fix: fall back to distribution ID when os-release has no version field @​cxzhong (#​961)

🚀 Enhancements

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates


Configuration

📅 Schedule: (in timezone Europe/Stockholm)

  • Branch creation
    • "after 09:00 and before 15:00 on monday, tuesday, wednesday and thursday,after 09:00 and before 13:00 on friday"
  • 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate.

kognic-github-app[bot]
kognic-github-app Bot previously approved these changes Aug 20, 2026
@kognic-github-app

kognic-github-app Bot commented Aug 20, 2026

Copy link
Copy Markdown

🚫 Agent review flagged concerns. A human should review.

Major bump v8.3.2→v10.0.1 spans two documented breaking changes: (1) v9.0.0 changed prune-cache default to false (may increase Actions cache usage/costs); (2) v10.0.0 disables automatic caching for pull_request_target, workflow_run, and release trigger events (security improvement but a behavioural break). Without seeing the full workflow triggers and whether prune-cache or cache settings are explicitly configured, a human should confirm the breaking changes don't affect this build-publish.yml. No security compromise signals in chatter.

Sources:

Package Ecosystem Source repo Verification
astral-sh/setup-uv npm github.com/astral-sh/setup-uv chatter+changelog

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