From 03748a10cf00f78d373e5506a551d0730b988fce Mon Sep 17 00:00:00 2001 From: Dylan Verheul Date: Sun, 11 Oct 2026 11:12:27 +0200 Subject: [PATCH] Say what release-check reports straight after a cut 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) --- CHANGELOG.md | 4 ++++ MAINTAINING.md | 5 +++++ 2 files changed, 9 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 36e57f1c..057c1b0f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,9 @@ # Changelog +## Unreleased + +- Say in MAINTAINING.md that `just release-check` reporting no `Unreleased` entries straight after a cut means nothing is pending, not that the changelog was lost. + ## 26.3 (2026-10-11) - **Breaking:** Drop support for Python 3.10, end of life since 2026-10-01. The floor is now Python 3.11. diff --git a/MAINTAINING.md b/MAINTAINING.md index 5874300e..4e212960 100644 --- a/MAINTAINING.md +++ b/MAINTAINING.md @@ -110,6 +110,11 @@ it half-updated. Dependabot reopens it on the next run. gate or a contributor policy belongs in the notes under tooling. django-marina 26.3 shipped with nine such changes unrecorded, and django-bootstrap4 and django-bootstrap5 each found four or five more of their own, because the recipe only showed the first group. + Straight after a cut, in the window between merging the release PR and pushing the tag, this + prints `(none)` for the `Unreleased` entries next to every commit since the previous tag. + That is correct and it means nothing is pending: stamping the section removed the heading the + recipe looks for, and the tag it compares against is still the old one. It does not mean the + changelog was lost. 2. On a release branch, update `CHANGELOG.md`, bump `version` in `pyproject.toml`, and run `just relock` so `uv.lock` names the new version; open a PR and merge it. `uv sync --frozen` does not check the project's own version, so a stale lock otherwise survives every packaging