Upgrade release workflow to actions/checkout v7#767
Merged
1 commit merged intoJul 23, 2026
Merged
Conversation
GitHub-hosted runners now force Node 20 actions onto Node 24. Upgrade both release jobs to checkout v7 while leaving the Clawith project Node configuration unchanged. Constraint: The release workflow creates branches, pull requests, tags, and releases when run live. Rejected: actions/checkout@v6 | v7 is the current GitHub-recommended stable major. Confidence: high Scope-risk: narrow Reversibility: clean Directive: This changes only the checkout action runtime; do not couple it to the project Node version. Tested: YAML parse and job assertions, repository-wide checkout reference scan, git diff --check. Not-tested: Live release workflow because it has release side effects.
Y1fe1Zh0u
added a commit
that referenced
this pull request
Jul 22, 2026
The integration branch needs this pull request alongside the other v1.11.2 candidates without changing the original PR state. Constraint: Preserve the source PR commit and merge in numeric order. Confidence: high Scope-risk: moderate Related: #767 Tested: Git merge completed without unresolved conflicts Not-tested: Combined backend and frontend suites pending
Y1fe1Zh0u
closed this pull request by merging all changes
into
dataelement:main
in
40c1f6b
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
actions/checkout@v4toactions/checkout@v7Why
actions/checkout@v4targets the deprecated Node.js 20 action runtime, so GitHub-hosted runners emit a warning while forcing it onto Node.js 24. Checkout v7 declares the supported Node.js 24 runtime and is the current stable major recommended by GitHub.The v7 fork-checkout safeguard applies to
pull_request_targetandworkflow_run; this workflow usesworkflow_dispatchandpull_request: closed, so its current triggers are unaffected.Impact
The release workflow no longer relies on the deprecated Node.js 20 checkout runtime. This does not change the Node.js version used by Clawith itself.
Validation
.github/workflows/release.ymland asserted both checkout steps use v7actions/checkoutreference remainsgit diff --checkThe live Release workflow was not triggered because it can create release branches, pull requests, tags, and releases.