fix(ci): the workflow stops running on a runtime GitHub already replaced - #70
Merged
Merged
Conversation
Every run has been printing the same warning: actions/checkout@v4 and actions/setup-node@v4 target Node.js 20, the runner forces them onto Node.js 24, and Node 20 is deprecated. Nothing was red, which is why it sat in the intake since 2026-07-27, but the deprecation is a date that has already passed rather than an opinion, and a warning on every run is a signal nobody reads after the third time. Both actions go to v7, which is the current major for each, published 2026-07-14 and 2026-07-20. The intake row proposed the v5 line and this session repeated that from the row instead of asking the source, which is the exact mistake the stack skill exists to prevent: v5 was already two majors behind on the day the row was written down. Checked against the tag list and the release notes of both repositories before bumping. Neither major touches how they are called here, and the calls are as plain as they get: checkout with no inputs except fetch-depth on the trace job, setup-node with a version. What this deliberately does not change is node-version: 20, the runtime the gates themselves run on. That is a separate question with a real consequence, because README.md promises anyone copying this framework that Node 20 is enough, and moving it means testing the gates on the new version and changing that promise in the same breath. Left in the intake as the open half of that row, so this change stays what it says it is. Traces-to: SC-6
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.
What changed and why
actions/checkoutandactions/setup-nodego from v4 to v7, in all three jobs. Nothing else.Every run has been printing the same warning:
Nothing was red, which is why it sat in the intake since 2026-07-27. But GitHub is already
forcing the swap, so this is a date that has passed rather than an opinion, and a warning that
fires on every run is a signal nobody reads after the third time.
One correction worth recording. The intake row proposed "the v5 line", and this session
repeated that from the row instead of asking the source. v5 was already two majors behind on the
day that row was written. The current majors are v7 for both, published 2026-07-14 and
2026-07-20, checked against each repository's tag list and release notes before bumping. That is
exactly the mistake
stackexists to prevent, made here on a version number.What this deliberately does not change:
node-version: 20, the runtime the gates themselvesrun on. That is the other half of the same intake row and it has a real consequence, because
README.mdpromises anyone copying Groundwork that Node 20 is enough. Moving it means testingthe gates on the new version and changing that promise in the same change. It stays open.
Verified by
node checks/check.mjsgreen locally, but the real proof of a workflow change is the workflowitself: this PR runs
gate,traceanddrillon the new actions, which is all nine suitesplus the checks plus a full copy-route walk. If v7 changed anything that matters here, one of
those goes red on this PR rather than on
main.The one thing to read on this run rather than assume: whether the deprecation warning is gone
from the annotations, and whether
setup-node@v7still resolvesnode-version: 20. Both areanswered by the run attached to this PR, and I will confirm them before this is merged.