Skip to content

fix: bump generated checkout pin to v6.0.3 to match committed workflows - #95

Merged
joshua-temple merged 1 commit into
mainfrom
fix/generator-action-pins
Jun 10, 2026
Merged

joshua-temple merged 1 commit into
mainfrom
fix/generator-action-pins

Conversation

@joshua-temple

Copy link
Copy Markdown
Collaborator

The generator's built-in pin table held actions/checkout at v4.3.1, but dependabot had already moved the committed self-host workflows to v6.0.3. Regenerating the workflows would silently downgrade checkout back to v4, undoing the bump.

Updates the pin-table entry to the v6.0.3 SHA the hand-written workflows already pin (df4cb1c0...), so tag mode emits @v6 and SHA mode emits the v6.0.3 commit. Generated orchestrate.yaml/promote.yaml now match the committed actions/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 produces actions/checkout@v6, matching the committed files.

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>
@joshua-temple
joshua-temple merged commit e30dd6b into main Jun 10, 2026
6 checks passed
@joshua-temple
joshua-temple deleted the fix/generator-action-pins branch June 10, 2026 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant