ci: bump actions/checkout v4 → v6 + opt JS actions into Node 24#128
Merged
Conversation
CI annotation on the last few runs warns that Node.js 20 actions are deprecated and will be forced to Node.js 24 by default on 2026-06-02. The annotation listed five affected actions: * `actions/checkout@v4` — used directly in both our workflows * `actions/cache@5a3ec84e`, `actions/deploy-pages@d6db9016`, `actions/upload-artifact@v4`, `ruby/setup-ruby@eaecf785f` — used transitively from `leanprover/lean-action@main` and `leanprover-community/docgen-action@main`; we can't bump those directly. Changes: * Bump our `actions/checkout@v4` → `actions/checkout@v6` (latest is v6.0.2; v6 supports Node.js 24). * Add `env: FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'` at the workflow level in both `blueprint.yml` and `blueprint-check.yml`. This is the GitHub-recommended interim opt-in until the third-party actions ship Node.js 24 builds, after which the env var can come out. Net: 2 files, +14 / −2.
Missed in the previous commit (Edit tool needed a Read first). Same two-line change as blueprint.yml: bump `actions/checkout@v4` → `@v6` and add the workflow-level `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` env.
Per GitHub's Node 20 deprecation changelog, the `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` opt-in remains correct but the default switchover is 2026-06-16, not 2026-06-02 as the comments said. Comment-only change in both workflows; the env var stays.
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
CI annotations on recent runs warn that five Node.js 20 actions will be force-bumped to Node.js 24 on 2026-06-02 (6 days from now). Getting ahead of that with a small two-file change.
actions/checkout@v4@v6(latest is v6.0.2, supports Node 24)actions/cache@5a3ec84e,actions/deploy-pages@d6db9016,actions/upload-artifact@v4,ruby/setup-ruby@eaecf785fleanprover/lean-action@mainandleanprover-community/docgen-action@main)env: FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'(GitHub-recommended interim opt-in)Once the third-party actions ship Node 24 builds, the env var can come out. Documented inline in both files.
Net: 2 files, +14 / −2.
Test plan
yaml.safe_loadparses both workflows cleanlyblueprint-check.yml)