ci: bump checkout to v7 - #53
Merged
Merged
Conversation
Align to the current major of actions/checkout (Node 24 runtime, ESM). The v7 breaking change concerns safer pull_request_target/workflow_run checkout defaults, which this push-only workflow doesn't use. The runner requirement (v2.327.1+) is satisfied by ubuntu-latest.
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.
Summary
Bump all
actions/checkoutreferences from@v4to@v7(current major; latest v7.0.1).Jobs updated
All four checkouts in
.github/workflows/ci.yml:run_checksupload_to_pypipush_to_docker_hubpush_to_enapter_docker_hubBreaking-change analysis
pull_request_target/workflow_runevents (newallow-unsafe-pr-checkoutinput). This workflow triggers onpushonly and does not usepull_request_targetorworkflow_run, so it is unaffected.ubuntu-latestsatisfies this.Notes
Only
run_checksis PR-visible in CI; the Docker jobs are tag-gated (refs/tags/v), so they'll be exercised on the next release.