chore(deps): update astral-sh/setup-uv action to v8#668
chore(deps): update astral-sh/setup-uv action to v8#668renovate-bot-cbcoutinho[bot] wants to merge 1 commit intomasterfrom
Conversation
|
PR Review: chore(deps): update astral-sh/setup-uv action to v8 This is a straightforward, low-risk dependency update from Renovate Bot. Summary: Updates astral-sh/setup-uv from v7.6.0 to v8.0.0 across 3 workflow files (rag-evaluation.yml, release.yml, test.yml). All 5 occurrences are updated consistently. Security: This is a security improvement. v8.0.0 introduces immutable releases, preventing supply chain attacks like the tj-actions incident. Major/minor version tags are no longer published by the action maintainers, forcing users to pin to exact versions or commit hashes. The repo was already using commit hash pinning, so the transition is seamless. Breaking Changes: v8 removes the old manifest-file format. Since the workflows only use setup-uv for basic installation with no custom manifest files configured, this breaking change does not apply here. Potential Issues: None identified. This is a CI-only change with no impact on application code, tests, or runtime behavior. Verdict: Safe to merge. Low risk, security-positive update with no application impact. |
e61d8a6 to
a963c63
Compare
PR Review: chore(deps): update astral-sh/setup-uv action to v8This is a straightforward Renovate-managed CI dependency update. Here's a quick review: SummaryUpdates ObservationsSecurity (positive): The action is pinned to a specific commit SHA ( Consistency: All 5 occurrences across the 3 files are updated uniformly — no stragglers left on the old version. Breaking changes: v8.0.0 removed support for the old Functional changes: The new VerdictLGTM. Low-risk, appropriate dependency update. Safe to merge. |
This PR contains the following updates:
v7.6.0→v8.1.0Release Notes
astral-sh/setup-uv (astral-sh/setup-uv)
v8.1.0: 🌈 New inputno-projectCompare Source
Changes
This add the a new boolean input
no-project.It only makes sense to use in combination with
activate-environment: trueand will append--no projectto theuv venvcall. This is for example useful if you have a pyproject.toml file with parts unparseable by uv🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
v8.0.0: 🌈 Immutable releases and secure tagsCompare Source
This is the first immutable release of
setup-uv🥳All future releases are also immutable, if you want to know more about what this means checkout the docs.
This release also has two breaking changes
New format for
manifest-fileThe previously deprecated way of defining a custom version manifest to control which
uvversions are available and where to download them from got removed. The functionality is still there but you have to use the new format.No more major and minor tags
To increase security even more we will stop publishing minor tags. You won't be able to use
@v8or@v8.0any longer. We do this because pinning to major releases opens up users to supply chain attacks like what happened to tj-actions.🚨 Breaking changes
🧰 Maintenance
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate.