Backport v20.0.1 #1120
Closed
Backport v20.0.1 #1120
Conversation
This file contains 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
Closed
mollykarcher
approved these changes
Dec 11, 2023
There was a problem hiding this comment.
I don't see the conflict you're referencing with #1119, but also don't see an issue with merging this one instead of that one
|
ok, I'll merge, I saw conflict on cargo.lock when I rebased main locally and assumed that would have popped up when merging main into release/v20.0.1, but didn't verify that |
|
will redo this version bump back to main based on 20.0.2 |
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.
What
back port the v20.0.1 to main
Why
the gh bot pr to do the same backport has fallen behind main and would have a conflict - #1119 , doing it here as a rebase on top of latest main instead.
Known limitations