build(deps): bump actions/checkout to v7.0.0 and github-script to v9.0.0 - #402
Merged
Merged
Conversation
joshua-temple
changed the base branch from
refactor/converge-artifact-versions
to
main
June 27, 2026 22:07
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
build/bump-checkout-github-script
branch
from
June 27, 2026 22:08
fab343e to
d8e52b1
Compare
joshua-temple
enabled auto-merge (squash)
June 27, 2026 22:09
This was referenced Jun 27, 2026
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.
Problem
actions/checkout was pinned to v6.0.3 (SHA df4cb1c) and actions/github-script to v7.1.0 (SHA f28e40c). checkout v7 and github-script v9 are Node 24 actions; the Node-24 act image pin from #399 makes these safe to run.
Fix
internal/generate/action_pins.yaml: checkout v6.0.3 -> v7.0.0 (9c091bb), github-script v7.1.0 -> v9.0.0 (3a2844b)orchestrate.yamlandpromote.yaml(the two cascade-generated workflows).githubworkflows and the composite action to the new SHAs; consistency lint (TestWorkflowsConsistentWithActionPins) is the guard and passesVerification
Local bar:
go build ./...cleango test ./...2021 tests passgolangci-lint run ./...no issuesactionlintfindings on orchestrate/promote/build-cli are pre-existing on the base branch (same 6 findings, unrelated to this change)Docker e2e (act + gitea + Node-24 catthehacker image, actRunnerNodeMajorMin=24):
TestMultiStepScenarios/Two_Environment_Happy_Path- PASS (act executes the generated orchestrate workflow, checkout v7 runs on Node 24)TestMultiStepScenarios/Action_pins:_sha_mode_pins_to_an_immutable_commit(scenario 35) - PASSTestMultiStepScenarios/Action_pins:_default_mode_emits_the_mutable_major_tag(scenario 36) - PASSTestMultiStepScenarios/Action_pins:_per-action_override_is_honored_over_the_pin_mode(scenario 39) - PASS5/5 passed. github-script v9 does not appear in any act-executed generated workflow (orchestrate/promote use only checkout); it appears only in the hand-written
drift-comment.yamlwhich does not run under the local harness.Resolved SHAs (verified via
git ls-remote):actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0(v7.0.0)actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3(v9.0.0)Bases on
refactor/converge-artifact-versions(#401); rebases onto main after that merges.