ci: track the current action pins - #96
Merged
Merged
Conversation
checkout v7.0.0 -> v7.0.1, deploy-pages v5.0.0 -> v5.0.1, setup-python v6.3.0 -> v7.0.0, setup-uv v8.3.0 -> v10.1.0. setup-uv v9 flips prune-cache to false and v10 disables the automatic cache for pull_request_target, workflow_run and release. Neither reaches here: every call site sets enable-cache explicitly, and the one that does not runs on pull_request and push.
ajbarea
force-pushed
the
chore/action-pin-drift
branch
from
September 20, 2026 02:23
708b875 to
6796018
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four actions had fallen behind the rest of the fleet,
setup-uvby two majors. Dependabot has never opened agithub-actionsPR here, so the pins drifted silently while theuvecosystem stayed current.actions/checkoutactions/deploy-pagesactions/setup-pythonastral-sh/setup-uvThe two
setup-uvmajors carry behaviour changes that do not reach this repo: v9 flipsprune-cachetofalse, which only affects cache size, and v10 disables the automatic cache forpull_request_target,workflow_runandrelease. Every call site here setsenable-cacheexplicitly, and the single one that does not (zizmor.yml) runs onpull_requestandpush.setup-pythonv7 is already green on techne, periplus and pharos.