generalize upgrade to take more than one lib pair simultaneously#5963
Merged
generalize upgrade to take more than one lib pair simultaneously#5963
Conversation
Contributor
|
Nice! Could you explain the different cases with the different messages; I guess when there's underscores in the arg names, then it doesn't try to "rename", and then under certain circumstances it does? And then I think we should probably not have a bulleted list with just one bullet. |
Member
Author
|
Regarding renaming, it's the same behavior as before - if the library you are upgrading to ends in |
Member
Author
Ok, I just replaced it with a comma-separated list then, like in the successful upgrade message |
aryairani
approved these changes
Oct 30, 2025
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
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.
Overview
This PR generalizes
upgradeto allow upgrading multiple libraries simultaneously:(it's an error to provide an odd number of arguments).
One small user-visible implementation quirk: if an upgrade fails, we had been putting the user on a branch called
upgrade-<old>-to-<new>to resolve it, as a reminder about the branch context. However, I didn't want to continue that template for an arbitrary number of library upgrades, so if a 2+ library upgrade fails, the user is just put on a branch calledupgrade(orupgrade__2ifupgradeis taken, etc).Test coverage
I've added tests to the
upgrade.mdtranscript.