ci: bump actions/checkout to v6 and actions/setup-dotnet to v5#43
Merged
Conversation
GitHub deprecated the Node.js 20 runtime on Actions runners on 2025-09-19. actions/checkout@v4 and actions/setup-dotnet@v4 still declare Node 20, so the runner emits a warning and a FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 shim is needed to keep them working. Upgrading to checkout@v6 and setup-dotnet@v5 — both of which natively target Node 24 — removes the warning and lets us drop the env shim from both workflows. No functional change to the build, test, or release pipeline; this is pure toolchain hygiene.
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.
GitHub deprecated the Node.js 20 runtime on Actions runners on 2025-09-19. actions/checkout@v4 and actions/setup-dotnet@v4 still declare Node 20, so the runner emits a warning and a FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 shim is needed to keep them working. Upgrading to checkout@v6 and setup-dotnet@v5 — both of which natively target Node 24 — removes the warning and lets us drop the env shim from both workflows.
No functional change to the build, test, or release pipeline; this is pure toolchain hygiene.
Description
Brief description of the changes in this PR.
Type of change
Testing
Describe the tests you ran to verify your changes.
dotnet test)dotnet build PassKey.sln -p:Platform=x64)Checklist