Date the 0.7.0 release - #149
Merged
Merged
Conversation
…development The generator reads the newest dated changelog heading, which is what keeps it from claiming a release PyPI does not have. The tag is pushed and PyPI has the wheel, so the heading carries its date now.
|
Warning Review limit reachedNext included review available in 9 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
The tag is pushed and PyPI has
ctrlrun 0.7.0(wheel and sdist, uploaded 2026-09-11T23:46Z), so the changelog heading carries its date.This is the half of the release that belongs to the tag rather than to the release PR:
render_readinessdeliberately reads the newest dated heading, so that the site can never claim a release PyPI does not have. Until now it correctly said "0.7.0 is in development; PyPI has 0.6.1". With the date it reads 0.7.0, confirmed against the generator.A matching docs PR regenerates the readiness block.