Update GitHub Actions runtimes - #75
Merged
Merged
Conversation
thossullivan
marked this pull request as ready for review
August 18, 2026 02:47
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.
What changed
actions/checkout@v7actions/setup-node@v7actions/upload-artifact@v7actions/download-artifact@v8Why
The live hosted consumer UAT passed, but GitHub annotated the copied bot workflow because its
@v4actions still used the deprecated Node 20 action runtime. The repository's executable workflows had already moved forward; the README, examples, and packaged bot template had drifted.Node 20 itself reached EOL on April 30, 2026. Disabling automatic npm-cache discovery also keeps a consumer repository's package metadata from silently changing the behavior of the read-only eval or write-capable publish jobs.
Validation
npm testnode bot/test/package.mjs