Skip to content

release: 26.4 #877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dyve wants to merge 1 commit into from
+5 −5
Closed

release: 26.4 #877

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
3 changes: 1 addition & 2 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"]
Expand Down Expand Up @@ -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",
Expand Down
2 changes: 1 addition & 1 deletion uv.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading