chore(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0 in the github-actions group across 1 directory - #1888
Conversation
There was a problem hiding this comment.
Looks good, straightforward dependency version bump. Reviewed both workflow files: the SHA pin for astral-sh/setup-uv is updated consistently across all 5 usages (4 in ci.yml, 1 in release.yml) and each new SHA matches its # v10.1.0 comment; no other logic or job configuration changed.
Extended reasoning...
Overview
The diff touches only .github/workflows/ci.yml and .github/workflows/release.yml, updating the pinned commit SHA for the astral-sh/setup-uv GitHub Action from 20cfd1bf945f4377ade1205e4dbc17946fc9a30d (v10.0.1) to bec219d24cd3e171d82865faccec33120bb574f4 (v10.1.0) in five separate job steps. This is a standard Dependabot-generated dependency bump within a github-actions update group. No application or library source code, no with: parameters, and no job logic were modified.
Security risks
None identified. The action reference remains fully pinned to an immutable commit SHA (not a mutable tag), which is the security best practice already in place and preserved here. The new SHA corresponds to the tagged v10.1.0 release per the PR description, and the accompanying comment is updated to match. No secrets, permissions, or credential handling are touched by this change.
Level of scrutiny
Low. This is a mechanical, repetitive change (same SHA substitution repeated 5 times) with no semantic differences beyond the version bump. It is exactly the kind of change dependency-update bots produce routinely and matches the pattern of prior, presumably already-merged bumps in this repo's history.
Other factors
The bug hunting system reported no findings, and my own diff review confirms all five occurrences were updated consistently and correctly, with no strays left on the old SHA. There's no CODEOWNERS restriction noted for workflow files, and the change carries no functional risk to build/test/release behavior beyond whatever astral-sh/setup-uv itself changed between these versions (proxy handling fix and a new output), which is out of scope for this repo to verify further.
Bumps the github-actions group with 1 update in the / directory: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv). Updates `astral-sh/setup-uv` from 10.0.1 to 10.1.0 - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@20cfd1b...bec219d) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: 10.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
0ee5cf2 to
4309ede
Compare
wochinge
left a comment
There was a problem hiding this comment.
Straightforward minor GitHub Actions bump (astral-sh/setup-uv v10.0.1 → v10.1.0), correctly pinned to a full commit SHA with matching version comment across all 5 usages. Changelog is bug fixes + security hardening only, no breaking changes. Re-triggered CI under my account since dependabot-run jobs lack live-provider secrets; the one remaining failure (test_audio_input_and_output) was a flaky live-provider test unrelated to this change and passed on rerun.
Bumps the github-actions group with 1 update in the / directory: astral-sh/setup-uv.
Updates
astral-sh/setup-uvfrom 10.0.1 to 10.1.0Release notes
Sourced from astral-sh/setup-uv's releases.
Commits
bec219dchore(deps-dev): roll up Dependabot updates (#1043)b90ec40fix: respect no proxy directive (#1037)421feb6chore: update known checksums for 0.12.12 (#1041)f634bf4Expose a Python "identity" output (#1036)a6772c8chore: update known checksums for 0.12.10/0.12.11 (#1038)e105c8fchore: update known checksums for 0.12.9 (#1035)cd13f92Verify downloads with astral-sh/versions checksums (#1033)3aef7b9chore: update known checksums for 0.12.7/0.12.8 (#1031)d08d816chore: update known checksums for 0.12.6 (#1030)19b4d1eHarden npm install defaults (#1026)