Update Node.js version from 20 to 24#228
Open
kuboon wants to merge 1 commit intodevcontainers:mainfrom
Open
Conversation
dnegstad
pushed a commit
to dnegstad/devcontainer-dev-certs
that referenced
this pull request
May 5, 2026
devcontainers/action@v1.4.3 is still a node20 action; GitHub Actions deprecates node20 in September. The upstream Node 24 migration (PR devcontainers/action#228) is open but unreleased. The action is a thin wrapper around the @devcontainers/cli, so swap it for the CLI directly. The CLI runs under the runner's installed Node (22 today, 24 next), which sidesteps the deprecation entirely. The publish-feature job already had docker/login-action handling GHCR auth, and the existing buildx-imagetools step still resolves the published manifest digest for attestation. Pinning @devcontainers/cli to 0.86.0 to match the supply-chain hygiene goals of the rest of this branch.
dnegstad
added a commit
to dnegstad/devcontainer-dev-certs
that referenced
this pull request
May 5, 2026
* Bump pinned action versions and SHA-pin setup-dotnet Brings every action reference current with its latest tag and converts the remaining tag-pinned actions/setup-dotnet references to a full-length SHA so the workflows stay compliant if the SHA-pin policy is reinstated. - actions/setup-node: v6.3.0 → v6.4.0 (minor) - actions/setup-dotnet: v4 (tag-pinned) → v5.2.0 (SHA-pinned). v5 only drops support for legacy .NET versions; we install 10.0.x, so unaffected. The Node 24 / runner v2.327.1+ requirement is satisfied by GitHub-hosted ubuntu-latest and windows-latest. - peter-evans/create-pull-request: v7.0.11 → v8.1.1 (major). No input-shape changes for the inputs bump-version.yml uses (branch, commit-message, title, body, delete-branch). Same Node 24 / runner constraint. * Replace devcontainers/action with devcontainer CLI devcontainers/action@v1.4.3 is still a node20 action; GitHub Actions deprecates node20 in September. The upstream Node 24 migration (PR devcontainers/action#228) is open but unreleased. The action is a thin wrapper around the @devcontainers/cli, so swap it for the CLI directly. The CLI runs under the runner's installed Node (22 today, 24 next), which sidesteps the deprecation entirely. The publish-feature job already had docker/login-action handling GHCR auth, and the existing buildx-imagetools step still resolves the published manifest digest for attestation. Pinning @devcontainers/cli to 0.86.0 to match the supply-chain hygiene goals of the rest of this branch. --------- Co-authored-by: Claude <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.
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/