fix: bump generated checkout pin to v6.0.3 to match committed workflows - #95
Merged
Merged
Conversation
The generator pinned actions/checkout at v4.3.1 while dependabot had moved the committed self-host workflows to v6.0.3, so regenerating would silently downgrade checkout. Update the built-in pin table to the v6.0.3 SHA the workflows already use. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
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.
The generator's built-in pin table held
actions/checkoutatv4.3.1, but dependabot had already moved the committed self-host workflows tov6.0.3. Regenerating the workflows would silently downgrade checkout back to v4, undoing the bump.Updates the pin-table entry to the
v6.0.3SHA the hand-written workflows already pin (df4cb1c0...), so tag mode emits@v6and SHA mode emits the v6.0.3 commit. Generatedorchestrate.yaml/promote.yamlnow match the committedactions/checkout@v6. Two SHA-mode test assertions are updated to the new pin.Scope is limited to
checkout, the only action that drifted in the self-host workflows. The artifact and github-script pins are left as-is since they aren't emitted by cascade's own manifest and the repo offers no verified newer version to bump them to.Verification:
go build ./...clean,go test ./internal/...green (1008), and regenerating the self-host workflows producesactions/checkout@v6, matching the committed files.