[Tooling] Update gems to latest non-breaking version #16349
Merged
Conversation
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
In particular, update `release-toolkit` to `13.7.0`
Collaborator
AliSoftware
changed the title
AliSoftware
added
the
category: tooling
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.
Description
While I was testing #16346, I got the reminder prompt that
release-toolkitwas not up-to-date and the suggestion to update it from13.5.1to13.7.0.This PR actually takes the occasion to update all the gems to their latest versions compatible with the
Gemfilerequirements — by just runningbundle updateon the repo, nothing more.Test Steps
Given we didn't update anything to a breaking-change version, as long as CI is green we should be good to go.