Repository navigation
Allow gh-issue 0 for "no changes" release entries - #92
Merged
Merged
Conversation
Yhg1s
approved these changes
Oct 9, 2026
Yhg1s
pushed a commit
to python/cpython
that referenced
this pull request
Oct 9, 2026
Needed for 3.15.0 final release, which has no new NEWS fragments from rc3. See python/blurb#92. Updated with make -C Doc lock Also routinely updates idna and sphinx-linklint.
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.
For the 3.15.0 release, which has no new
NEWSfragments since rc3.blurb releasewrites a placeholder entry withgh-issue: 0when there are noNEWSfragments, but the minimum issue number check added in #519 rejected it, so the release failed on reload.