Adding changelog entries for merges since 0.28.0 #2202
Merged
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
jmartinesp
reviewed
Aug 1, 2024
I'm hoping to do a 0.28.1 release and these would be good to have in it. I also considered adding an entry for the work that mgeisler has been doing, but I couldn't think of a good wording for that.
bendk
force-pushed
the
0.28.1-changlog-entries
branch
from
fcea2ed
to
4f97413
Compare
mhammond
approved these changes
Aug 1, 2024
A 0.29 might not hurt before we land the breaking changes queued up too (I'm thinking the custom type changes) - I also just noticed I screwed up some changelog entries which are listed as being in 0.28 but are not! I'll try and remember to put a PR up to fix that. |
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.
I'm hoping to do a 0.28.1 release and these would be good to have in it.
I also considered adding an entry for the work that @mgeisler has been doing, but I couldn't think of a good wording for that. @mgeisler do you have any suggestions for changelog entry text?