Skip to content

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

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

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

Conversation

@renovate

@renovate renovate Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
astral-sh/setup-uv action patch v10.3.0 → v10.3.3

Release Notes

astral-sh/setup-uv

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • 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 requested a review from hanthor as a code owner October 21, 2026 23:51
@renovate
renovate Bot enabled auto-merge (squash) October 21, 2026 23:51
@hanthor-hive-agent

Copy link
Copy Markdown
Contributor
28146b2

⚠️ Sentinel alert — maintainer review required

Hive flagged this PR (author @renovate[bot], head 28146b2e1657) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 2 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/ci.yml
    • .github/workflows/server-images.yml

Hive added the sentinel-alert label. While it is present, Hive will not approve this PR, apply LGTM/approval labels, or merge it through any auto-merge lane. Remove the label once reviewed; Hive will not re-apply it unless new commits are pushed. Tune paths and behaviors under sentinel in hive.yaml or the dashboard Security tab.

@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v10.3.1 chore(deps): update astral-sh/setup-uv action to v10.3.2 Oct 22, 2026
@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 2 times, most recently from 7f56eb9 to 462ccb9 Compare October 22, 2026 22:32

@hanthor-hive-agent hanthor-hive-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:75 and .github/workflows/server-images.yml:100, both astral-sh/setup-uv@v10.3.0 → @v10.3.2. Nothing else in either file changes — no triggers, no permissions: block, no new steps, no run: text.
  • The sentinel fired on sensitive_path (any edit under .github/workflows), and its comment was written against head 28146b2e1657; renovate has since pushed 462ccb9. The facts below are read from the current head.

Blast radius, verified in the tree

  • ci.yml sets workflow-level permissions: contents: read (ci.yml:18-19); the bumped step is in the tests job, which declares no job-level override.
  • server-images.yml sets permissions: contents: read (:28-29); the bumped step at :100 is in the installer-acceptance job (:32), which also declares no override. The only privileged job in that file, publish (contents: write, packages: write, :401-403), does not use setup-uv — grep finds exactly two setup-uv references 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.2 is 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

@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch from 462ccb9 to 0192dc7 Compare October 23, 2026 00:54

@hanthor-hive-agent hanthor-hive-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:75 and .github/workflows/server-images.yml:100. No triggers, steps, secrets or permissions changed — permissions: contents: read is untouched at ci.yml:18-19 and server-images.yml:28-29, and the contents: write/packages: write job block at server-images.yml:401-403 is not in the diff.
  • No version drift left behind: a whole-tree grep finds exactly two setup-uv references, 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-acceptance has no conclusion.
  • BLOCKED here is explained by .github/CODEOWNERS: — /.github/ @hanthor is 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

@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 10 times, most recently from 255d7ee to fd18e46 Compare October 28, 2026 18:33
@renovate renovate Bot changed the title chore(deps): update astral-sh/setup-uv action to v10.3.2 chore(deps): update astral-sh/setup-uv action to v10.3.3 Oct 28, 2026
@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 4 times, most recently from ec75400 to 5d3e263 Compare November 3, 2026 05:00
@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 5 times, most recently from bbbda70 to 6931933 Compare November 7, 2026 05:33
@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 8 times, most recently from ebaffbf to c91695c Compare November 13, 2026 13:08
@renovate
renovate Bot force-pushed the renovate/astral-sh-setup-uv-10.x branch 6 times, most recently from 2dfef6d to dc52aa9 Compare November 18, 2026 18:57

This branch has not been deployed

No deployments
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