chore: update codecov-action to v6 (Node.js 20 deprecation)#39
Merged
Conversation
…warning rubygems/release-gem@v1.2.0 internally pins older action versions; those warnings remain until the rubygems team ships an update. Co-Authored-By: Claude Sonnet 4.6 <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.
Summary
codecov/codecov-actionfrom@v5to@v6which targets Node.js 24, resolving one of the two Node.js 20 deprecation warnings in CIThe second warning (
rubygems/configure-rubygems-credentials) is an internal dependency ofrubygems/release-gem@v1.2.0(already the latest release). That warning will resolve once the rubygems team ships an update to their action. The existingFORCE_JAVASCRIPT_ACTIONS_TO_NODE24: trueenv var ensures both are already running on Node.js 24 functionally.🤖 Generated with Claude Code