Bump checkout to v7 and action-gh-release to v3 - #8
Merged
Merged
Conversation
Both were proposed by dependabot. Neither affects these workflows' behaviour: checkout v7's breaking change only concerns checking out fork pull requests under pull_request_target or workflow_run, which nothing here uses, and action-gh-release v3 only moves its runtime to Node 24, which the GitHub-hosted runners provide. Helped-By: claude-opus-5 <anthropic@willroscoe.uk>
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.
Picks up the two dependabot bumps that were closed (#1, #2), applied across all four workflows.
actions/checkoutpull_request_target/workflow_run. No workflow here uses either trigger.softprops/action-gh-releaseubuntu-latestprovides.actions/setup-pythonis already on v7 via #6.Lint, Test and Validate exercise the new checkout on this PR. The release workflow only runs on a push to
main, so its two changes are first exercised by the next version bump; ifaction-gh-release@v3were to fail there, the workflow can be re-run after reverting that one line, and no release would have been published.