Add just release-check as the first step of the release process - #882
Merged
Conversation
Propagated verbatim from django-marina. Two of four releases on 2026-08-28 shipped code changes with no changelog entry, caught only by diffing src/ against the last tag by hand. This makes that check one command and step 1 of the process.
|
coverage: 86.129%. remained the same — add-release-check 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.
Summary
Propagated from django-marina (zostera/django-marina#675), the canonical source for shared tooling. Both the
justfilerecipe and theMAINTAINING.mdrelease process are verbatim-synced perPACKAGING.md.Why it exists. Two of the four releases on 2026-08-28 shipped code changes with no changelog entry — django-bootstrap4 a
KeyErrorfix inurl_replace_param, django-icons aSafeStringrendering fix that was the most significant change in that release. Both were caught by hand, by diffingsrc/against the last tag. Nothing required that diff, and it takes several commands, so it does not get run mid-release.just release-checkmakes it one command and step 1.It is deliberately not a pass/fail gate — changelog entries do not reference commits, so nothing can mechanically prove coverage — and deliberately not wired into
just build, which runs in CI where a branch legitimately may not have its entry yet.Test plan
just release-checkruns and reports correctlyjust lintpasses