Update rubygems/configure-rubygems-credentials action to v2.1.0#98
Merged
olleolleolle merged 1 commit intoJun 20, 2026
Merged
Conversation
Contributor
Author
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
Bot
force-pushed
the
renovate/rubygems-configure-rubygems-credentials-2.x
branch
from
20d8661 to
b9e0c9d
Compare
renovate
Bot
deleted the
renovate/rubygems-configure-rubygems-credentials-2.x
branch
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.
This PR contains the following updates:
v2.0.0→v2.1.0Release Notes
rubygems/configure-rubygems-credentials (rubygems/configure-rubygems-credentials)
v2.1.0Compare Source
This release switches the action runtime from Node 20 to Node 24. The
node24declaration inaction.ymlremoves the deprecation warning that every consumer — most visibly throughrubygems/release-gem— has seen since GitHub announced the Node 20 deprecation, and gets ahead of runners switching JavaScript actions to Node 24 by default on June 16, 2026.Note for self-hosted runners: the
node24runtime requires actions/runner 2.327.1 or later. GitHub-hosted runners are unaffected.The pending major dependency updates are included as well: zod 4, @actions/core 3, and @actions/http-client 4. The actions toolkit majors ship only ES module builds now, so the build pipeline emits ES modules internally, while the bundled
dist/index.jsthe runner executes remains CommonJS. The action's inputs, outputs, and behavior are unchanged.Thanks to @dduugg for first proposing the runtime switch in #413.
What's Changed
Full Changelog: rubygems/configure-rubygems-credentials@v2.0.0...v2.1.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.