Repository navigation
release: 26.4 - #877
Closed
dyve wants to merge 1 commit into
Closed
release: 26.4#877dyve wants to merge 1 commit into
dyve wants to merge 1 commit into
Conversation
Three commits have touched src/ since v26.3 on 2026-08-28: addon support on floating-label fields, week/search/color inputs recognised as form controls, and the BOOTSTRAP5 system check. The test dependency group listed coverage[toml]>=7.6.1 twice. The duplicate is dropped and the group sorted alphabetically, matching the docs group next to it. Resolution does not change, only the lockfile's version of this package. Entries are reordered to the convention in MAINTAINING.md: the missing inline_field_class default first as a fix, then the three features, then tooling, then documentation. Verified with just lint and just build: check-manifest clean, pyroma 10/10, and both the wheel and the sdist smoke-test against an isolated environment. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Coverage Report for CI Build 35571032027Coverage remained the same at 96.208%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Member
Author
|
Closing, release postponed. Nothing here is wrong, it is just premature. Five PRs are open behind it (#878 through #882), four of which touch Redoing this is cheap when the time comes: The |
dyve
added a commit
that referenced
this pull request
Oct 4, 2026
…#885) 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>
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.
Three commits have touched
src/since v26.3 on 2026-08-28 and none of them have shipped: addon support on fields withlayout="floating",week/search/colorinputs recognised as form-control widgets, and thedjango_bootstrap5.W001system check.This converts
Unreleasedto## 26.4 (2026-09-21), bumpsversion, and reorders the entries to the convention in MAINTAINING.md. It also drops a duplicatecoverage[toml]>=7.6.1from thetestdependency group, which listed it twice, and sorts that group alphabetically to match thedocsgroup above it. Resolution is unaffected, the onlyuv.lockchange is this package's own version.Verified with
just lintandjust build: check-manifest reports the sdist matches version control, pyroma rates 10/10, and both the wheel and the sdist smoke-test in an isolated environment. Merging this does not publish anything,just release-tagonmaindoes that.🤖 Generated with Claude Code