Repository navigation
Say what release-check reports straight after a cut - #911
Merged
Merged
Conversation
Propagation of zostera/django-marina#696. In the window between merging the release PR and pushing the tag, just release-check prints "(none)" for the Unreleased entries next to every commit since the previous tag. Stamping the section removes the heading the recipe looks for, and the tag it compares against is still the old one. Correct, and it reads as if the changelog has been lost. Raised by the django-bootstrap4 session, which hit it while cutting 26.3. It does not show up in django-marina, where the tag sits on HEAD so both lists come back empty and the pair looks consistent. Documentation only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
coverage: 100.0%. remained the same — docs-release-check-after-a-cut into main |
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.
Propagation of zostera/django-marina#696.
In the window between merging the release PR and pushing the tag,
just release-checkprints(none)for theUnreleasedentries next to every commit since the previous tag. Stamping the section removed the heading the recipe looks for, and the tag it compares against is still the old one. Correct, but it reads as if the changelog had been lost.This is your own observation from cutting 26.3, written into MAINTAINING.md step 1 so the next person does not have to work it out. It does not show up in django-marina, where the tag sits on
HEADand both lists come back empty, so the pair looks consistent.The matching note about git silently filing a propagation's changelog entries under a freshly dated heading went into PACKAGING.md, which exists only in django-marina, so it is not part of this.
Documentation only. Verified with
just lint.🤖 Generated with Claude Code