Move one last release note for 0.45.0#11060
Merged
Merged
Conversation
In the lead up to the 0.45.0rc1 release we used the merge queue to pipeline the last 2 PRs that merged for the tag. However, this resulted in a single release note file merging before we could move it into the 0.45/ subdirectory. This commit fixes this so that the final PR for 0.45.0rc1 is correctly grouped in the 0.45 release notes subdirectory.
mtreinish
added
stable backport potential
Collaborator
|
One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 6580982459
💛 - Coveralls |
mergify Bot
pushed a commit
that referenced
this pull request
Oct 20, 2023
In the lead up to the 0.45.0rc1 release we used the merge queue to pipeline the last 2 PRs that merged for the tag. However, this resulted in a single release note file merging before we could move it into the 0.45/ subdirectory. This commit fixes this so that the final PR for 0.45.0rc1 is correctly grouped in the 0.45 release notes subdirectory. (cherry picked from commit 7585bd5)
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Oct 20, 2023
In the lead up to the 0.45.0rc1 release we used the merge queue to pipeline the last 2 PRs that merged for the tag. However, this resulted in a single release note file merging before we could move it into the 0.45/ subdirectory. This commit fixes this so that the final PR for 0.45.0rc1 is correctly grouped in the 0.45 release notes subdirectory. (cherry picked from commit 7585bd5) Co-authored-by: Matthew Treinish <mtreinish@kortar.org> Co-authored-by: Jake Lishman <jake.lishman@ibm.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
4 participants
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
In the lead up to the 0.45.0rc1 release we used the merge queue to pipeline the last 2 PRs that merged for the tag. However, this resulted in a single release note file merging before we could move it into the 0.45/ subdirectory. This commit fixes this so that the final PR for 0.45.0rc1 is correctly grouped in the 0.45 release notes subdirectory.
Details and comments