Repository navigation
chore(deps): update astral-sh/setup-uv action to v10.3.3 - #323
renovate[bot] wants to merge 1 commit into
Conversation
28146b2
|
7f56eb9 to
462ccb9
Compare
There was a problem hiding this comment.
Decision needed: @hanthor should decide whether to clear the sentinel-alert label on this renovate action bump and keep letting workflow action tags auto-update, or require SHA pinning for third-party actions in .github/workflows.
Routing this to a human because of the sentinel-alert label, not because I found a defect. Here are the facts so the decision is cheap.
What the diff actually is (head 462ccb9)
- Two lines:
.github/workflows/ci.yml:75and.github/workflows/server-images.yml:100, bothastral-sh/setup-uv@v10.3.0→@v10.3.2. Nothing else in either file changes — no triggers, nopermissions:block, no new steps, norun:text. - The sentinel fired on
sensitive_path(any edit under.github/workflows), and its comment was written against head28146b2e1657; renovate has since pushed462ccb9. The facts below are read from the current head.
Blast radius, verified in the tree
ci.ymlsets workflow-levelpermissions: contents: read(ci.yml:18-19); the bumped step is in thetestsjob, which declares no job-level override.server-images.ymlsetspermissions: contents: read(:28-29); the bumped step at:100is in theinstaller-acceptancejob (:32), which also declares no override. The only privileged job in that file,publish(contents: write,packages: write,:401-403), does not usesetup-uv— grep finds exactly twosetup-uvreferences repo-wide and both are bumped here, so no stale pin is left behind either.- Tag pinning matches the house convention in these same files (
actions/checkout@v7,actions/setup-go@v7,extractions/setup-just@v4), so this does not regress pinning posture — it also does not improve it:v10.3.2is a mutable tag, so the trust sits in astral-sh's tag, not in a commit SHA.
Correctness: patch bump; the release notes in the body describe a known-checksum table update for uv 0.13.5, and CI on this head is green. I see nothing wrong with the change itself.
— hive: agent=reviewer backend=omp model=anthropic/claude-opus-5:high omp=18.12.1
462ccb9 to
0192dc7
Compare
There was a problem hiding this comment.
Decision needed: @hanthor should decide whether to take the astral-sh/setup-uv v10.3.0 → v10.3.2 bump, since CODEOWNERS reserves /.github/ for your review and this PR edits two workflows.
Routing to a human: the change itself is clean, but it edits .github/workflows/ and carries sentinel-alert, so the trust call is not mine to make.
What I verified against the tree at 0192dc7:
- The diff is exactly two lines, both
uses:refs:.github/workflows/ci.yml:75and.github/workflows/server-images.yml:100. No triggers, steps, secrets or permissions changed —permissions: contents: readis untouched atci.yml:18-19andserver-images.yml:28-29, and thecontents: write/packages: writejob block atserver-images.yml:401-403is not in the diff. - No version drift left behind: a whole-tree grep finds exactly two
setup-uvreferences, and both are bumped. Nothing in docs pins the old version. - Tag pinning (
@v10.3.2) matches the repo idiom for every other action here (actions/checkout@v7,actions/setup-go@v7,extractions/setup-just@v4), so this PR introduces no new pinning weakness — it inherits the existing one. Not a finding against this change. - CI is green on the current head (lint, python, tests, osquery-smoke on both runners, deps-guard, justfile, tofu, broker);
installer-acceptancehas no conclusion. BLOCKEDhere is explained by.github/CODEOWNERS:—/.github/ @hanthoris listed under "Always owned, even inside carve-outs", so this cannot auto-merge by design.
One thing I did not verify: the upstream release content. The body's claim that v10.3.1/v10.3.2 only touch cached-checksum data and a cache-error path comes from the renovate-rendered release notes, not from reading the action's source. If that matters for a workflow that runs on master (pulled and applied with sudo by the fleet timer, per CODEOWNERS), it is worth a glance before merging.
No merge, label or close action taken.
— hive: agent=reviewer backend=omp model=anthropic/claude-opus-5:high omp=18.12.1
255d7ee to
fd18e46
Compare
ec75400 to
5d3e263
Compare
bbbda70 to
6931933
Compare
ebaffbf to
c91695c
Compare
2dfef6d to
dc52aa9
Compare
dc52aa9 to
5309dcf
Compare
This PR contains the following updates:
v10.3.0→v10.3.3Release Notes
astral-sh/setup-uv
v10.3.3: 🌈 Use Astral mirror for version manifests with GitHub fallbackCompare 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.5Compare Source
Changes
🧰 Maintenance
📚 Documentation
v10.3.1: 🌈 preserve cache error class names in save-cache bundleCompare 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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.