Repository navigation
Un-cut 26.4: fold the section back into Unreleased and return to 26.3 - #885
Merged
Merged
Conversation
main claimed a version that does not exist. CHANGELOG.md carried a closed `## 26.4 (2026-09-21)` section and pyproject.toml said 26.4, while the latest tag was v26.3 and nothing had been published. The release cut did not arrive through the release PR, #877, which was closed as postponed. It arrived through #878, the CI sync, which also carried the changelog heading, the version bump and the coverage[toml] dedup. Closing #877 therefore postponed nothing, and four more entries accumulated on top of a section that was already dated and closed. This folds the eight 26.4 entries back into Unreleased alongside the four that followed, ordered by the categories in MAINTAINING.md: bug fixes, then features, then tooling and internal. No entry text is changed. The version returns to 26.3 in pyproject.toml and uv.lock. `just release-check` reads correctly again. Before this it listed five src/ commits against an Unreleased section holding only two matching entries, because the other three were covered by the closed 26.4 section. uv.lock also bumps its own `revision` marker from 3 to 5, which my local uv wrote when regenerating. That is incidental to this change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Coverage Report for CI Build 37186483065Coverage remained the same at 96.233%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
This was referenced Oct 4, 2026
Merged
Merged
Merged
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.
What and why
mainclaims a version that does not exist.CHANGELOG.mdhas a closed## 26.4 (2026-09-21)section andpyproject.tomlsaysversion = "26.4", but the latest tag isv26.3and nothing has been published. Anyone installing from git gets a 26.4 that will later collide with the real one.The cut did not come from #877, the release PR, which was closed as postponed. It came from #878, the CI sync, which carried the dated changelog heading, the version bump and the
coverage[toml]dedup along with the workflow change. So closing #877 postponed nothing, and four further entries have since piled on top of a section that was already closed.This folds the eight 26.4 entries back into
Unreleasednext to the four that followed, ordered by the categories inMAINTAINING.md: bug fixes, then features, then tooling and internal. No entry text is changed, only the grouping and the order. The version returns to 26.3 inpyproject.tomlanduv.lock.Why it matters beyond tidiness
just release-checkwas actively misleading. It listed fivesrc/commits since v26.3 against anUnreleasedsection holding only two matching entries, because the other three were covered by the closed 26.4 section. A reader would conclude three changes had no changelog entry. After this it lists five commits against twelve entries that cover them.Verified
just lintclean, 176 tests pass, andjust buildnow producesdjango_bootstrap5-26.3artefacts with check-manifest, pyroma and both smoke tests passing.One incidental change
uv.lockalso bumps its ownrevisionmarker from 3 to 5, written by my local uv when regenerating after the version change. The only other difference is the package's own version. I left it rather than hand-editing a generated file, but it is unrelated to this change and worth knowing about.AI assistance
Yes. Written with Claude Code, as the trailer on the commit records.
🤖 Generated with Claude Code