From a9af392b149ba1e5f605f26ce752d0c9ce668890 Mon Sep 17 00:00:00 2001 From: Dylan Verheul Date: Mon, 21 Sep 2026 09:01:52 +0200 Subject: [PATCH] release: 26.4 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) --- CHANGELOG.md | 5 +++-- pyproject.toml | 3 +-- uv.lock | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3ede13cb..23520f78 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,11 +1,12 @@ # Changelog -## Unreleased +## 26.4 (2026-09-21) +- Add the documented `inline_field_class` setting to `BOOTSTRAP5_DEFAULTS`, where it was missing. Its effective default is unchanged. - Support `addon_before`/`addon_after` on fields with `layout="floating"` (#866). The `form-floating` element is now nested inside the `input-group`, as Bootstrap's floating-label input-group markup requires, instead of the two being alternatives. This removes the warning added in 26.3 (#833), which existed because the combination was unsupported. - Recognize `week`, `search` and `color` input-type widgets as form-control widgets, so `addon_before`/`addon_after` work on them, and warn instead of silently dropping addons on a widget that cannot have them (#743, #872). Floating labels stay unsupported for `color`, where Bootstrap sizes the swatch itself. - Add a system check that warns about keys in the `BOOTSTRAP5` setting that the package does not read, such as a setting removed in an earlier release or one carried over from django-bootstrap3 or django-bootstrap4 (`django_bootstrap5.W001`, #867). Silence it with `SILENCED_SYSTEM_CHECKS` if you keep extra keys deliberately. -- Add the documented `inline_field_class` setting to `BOOTSTRAP5_DEFAULTS`, where it was missing. Its effective default is unchanged. +- Drop a duplicate `coverage[toml]` entry from the `test` dependency group and sort it alphabetically. - Add `just release-check` to list `src/` changes against changelog entries before a release. - Fix the release process in MAINTAINING.md: the version bump goes through a PR, not a direct push to protected `main`. - Note in MAINTAINING.md why the `Django` dependency carries no upper bound. diff --git a/pyproject.toml b/pyproject.toml index 9da5c80d..d7b0d9af 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -32,7 +32,7 @@ license-files = ["LICENSE", "AUTHORS"] name = "django-bootstrap5" readme = "README.md" requires-python = ">=3.10" -version = "26.3" +version = "26.4" [project.optional-dependencies] jinja = ["Jinja2>=3.0,<4"] @@ -99,7 +99,6 @@ docs = [ "sphinx>=7.1.2", ] test = [ - "coverage[toml]>=7.6.1", "beautifulsoup4>=4.12.3", "coverage[toml]>=7.6.1", "pillow>=11.0.0", diff --git a/uv.lock b/uv.lock index 2f61c144..19903761 100644 --- a/uv.lock +++ b/uv.lock @@ -289,7 +289,7 @@ wheels = [ [[package]] name = "django-bootstrap5" -version = "26.3" +version = "26.4" source = { editable = "." } dependencies = [ { name = "django" },