Opt into Node.js 24 for JavaScript GitHub Actions#5
Merged
Conversation
Sets FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true at the workflow env level so all JavaScript-based actions (checkout, setup-dotnet, upload-artifact, download-artifact, action-gh-release) run under Node 24 instead of the deprecated Node 20 runtime. GitHub is auto-migrating JavaScript actions to Node 24 as the default on June 2, 2026 and removing the Node 20 runner entirely on September 16, 2026. Opting in now: - Removes the deprecation warnings from the most recent release runs. - Surfaces any Node 24 compatibility issues while there's still time to downgrade via ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. - No action version bumps needed — the flag reuses the existing v4/v2 pins, which continue working under Node 24. The flag becomes redundant once Node 24 is the default and should be removed then. A comment in the workflow documents this.
There was a problem hiding this comment.
Pull request overview
Updates the CI workflow to opt GitHub Actions’ JavaScript-based actions into the Node.js 24 runtime ahead of the scheduled Node 20 deprecation/removal, reducing runtime deprecation warnings during CI and releases.
Changes:
- Sets
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=trueat the workflowenvscope. - Adds inline documentation explaining the rationale and relevant migration dates.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Address PR #5 Copilot review: the original comment suggested setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true 'after Node 20 is removed from the runner on September 16, 2026' — but after that date the runtime is gone and the fallback can't work. Rewrite the comment to describe the narrow Jun 2 → Sep 16 escape hatch window correctly, and separate it from the 'this flag is temporary' note so each sentence has one purpose.
rodchristiansen
added a commit
that referenced
this pull request
Apr 12, 2026
Consolidates the four PRs merged today into a single semver entry for humans, and triggers a new CI release whose body will link back to the individual timestamp-tagged releases (2308, 2314, 2344, 2347). The entry credits @aysiu explicitly for the PEM client cert contribution in PR #2, which was the original spark for the mTLS feature. PFX + Credential Manager and the strategy-priority refactor were layered on as maintainer tweaks. Also documents: - xUnit test suite + dotnet test CI integration (PR #3) - Node.js 24 opt-in for JavaScript Actions (PR #5) - REG_DWORD/QWORD handling fix in GetRegistryValue, closing #4 (PR #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
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
Sets `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` at the workflow `env` level so all JavaScript-based actions (`actions/checkout`, `actions/setup-dotnet`, `actions/upload-artifact`, `actions/download-artifact`, `softprops/action-gh-release`) run under Node 24 instead of the deprecated Node 20 runtime.
Context
The last two release runs surfaced this deprecation warning:
Why the env flag instead of version bumps
Action version bumps (e.g. `actions/checkout@v4` → `@v5`) can be a separate, deliberate PR if/when new features from those majors are needed.
Test plan