[Merged by Bors] - Clarify that #445 was not released in 0.25.3 #493
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
Looks like the merge went slightly awry...
|
What do you mean with "slightly awry"? |
lfrancke
approved these changes
Oct 17, 2022
|
bors r+ Git decided to put the new changelog stuff into 0.25.3's added section rather than creating a new one. |
bors bot
pushed a commit
that referenced
this pull request
Oct 17, 2022
## Description Looks like the merge went slightly awry... Co-authored-by: Teo Klestrup Röijezon <teo.roijezon@stackable.de>
|
Pull request successfully merged into main. Build succeeded: |
bors
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Looks like the merge went slightly awry...
Review Checklist
Once the review is done, comment
bors r+(orbors merge) to merge. Further information