Skip to content

ci: bump actions/checkout to v6 and actions/setup-dotnet to v5#43

Merged
pexatar merged 1 commit into
mainfrom
ci/bump-actions-node24
May 16, 2026
Merged

ci: bump actions/checkout to v6 and actions/setup-dotnet to v5#43
pexatar merged 1 commit into
mainfrom
ci/bump-actions-node24

Conversation

@pexatar
Copy link
Copy Markdown
Owner

@pexatar pexatar commented May 16, 2026

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

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)

Testing

Describe the tests you ran to verify your changes.

  • All existing tests pass (dotnet test)
  • New tests added for new functionality
  • Solution builds without warnings (dotnet build PassKey.sln -p:Platform=x64)

Checklist

  • My code follows the project's code style guidelines
  • I have added XML documentation to all new public types and members
  • I have updated the CHANGELOG.md if applicable
  • My changes do not introduce new compiler warnings

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.
@pexatar pexatar merged commit 4813750 into main May 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant