Fix NEWS for recent releases#121
Merged
jelmer merged 1 commit intotesting-cabal:masterfrom Mar 3, 2026
Merged
Conversation
Member
|
@stephenfin I'm happy for you to cut tags (on the contrary!); I don't think we necessarily need a lot more process, but if we keep NEWS up to date that should help prevent races. |
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
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.
I had already pushed tags for the 4.3.0 and 4.3.1 and was not expecting to see a new 4.2.9 tag (which in hindsight would have been a better choice of version number than 4.3.0). Update the NEWS file to reflect these releases.
@jelmer I will do a better job of communicating when I do cut a tag in the future or just leave it to you if you'd prefer that. My apologies. I suspect we'll likely also want to delete tags and possibly yank releases. If we yank the 4.3.0 and 4.3.1 releases, we will not be able to use them for new releases so I suspect it would be better to instead delete the 4.2.9 tag and yank that release on PyPI.
This change is