fix(ci): resolve Node 20 deprecation warning#98
Merged
Conversation
…ecation warning GitHub Actions will force Node 20 actions to Node 24 by default starting June 16, 2026 and remove Node 20 from the runner on September 16, 2026. Updating actions/checkout and actions/setup-node to v5 eliminates the deprecation annotation without changing release semantics. Closes #97
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.
Closes #97
GitHub Actions will force Node 20 actions to Node 24 by default starting June 16, 2026, and remove Node 20 from the runner on September 16, 2026.
Updates both
actions/checkoutandactions/setup-nodefrom v4 to v5, which use the Node 24 runtime and eliminate the deprecation annotation.No change to release semantics — Trusted Publishing, build, and test steps remain identical.