Bump GitHub Actions to versions running on Node.js 24 - #3
Merged
Conversation
- actions/checkout: v4 → v6 - actions/setup-node: v4 → v6 - actions/upload-pages-artifact: v3 → v5 - actions/deploy-pages: v4 → v5 Resolves Node.js 20 deprecation warnings ahead of the June 2 2026 default flip and the September 16 2026 removal. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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/checkoutv4 → v6actions/setup-nodev4 → v6actions/upload-pages-artifactv3 → v5actions/deploy-pagesv4 → v5Resolves the Node.js 20 deprecation warnings now appearing on every workflow run. GitHub will force JavaScript actions to Node.js 24 by default on June 2, 2026 and remove Node.js 20 from runners on September 16, 2026. The v6/v5 action releases run on Node.js 24, so this bump gets ahead of both deadlines without needing the
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24escape hatch.Files touched:
.github/workflows/{ci,deploy,publish-design-system}.yml.Test plan
validate-latticeandlattice-lintjobs still pass