deps(deps): bump the python-minor-and-patch group across 1 directory with 22 updates

[dependabot]

Bumps the python-minor-and-patch group with 22 updates in the / directory:

Package	From	To
django-polish-inflection	0.1.0	0.1.1
django-denorm-iplweb	1.12.2	1.14.0
django-flexible-reports	0.4.1	0.4.2
django-dsl	0.1.14	0.1.15
django-dynamic-admin-columns	0.5.0	0.6.0
django-password-policies-iplweb	0.9.0	0.9.4
django-multiseek	0.10.2	0.10.3
django-redis-iplweb	6.0.1	6.0.2
djangorestframework	3.17.2	3.18.0
djangoql-iplweb	0.31.1	0.31.2
django-dbtemplates-iplweb	4.4.0	4.4.1
django-channels-broadcast	0.2.2	0.3.0
django-countdown	0.3.0	0.3.1
django-formdefaults	0.6.2	0.6.3
django-pg-baseline	0.3.0	0.3.1
django-site-blog	0.2.1	0.2.2
django-first-run-wizard	0.2.0	0.2.1
ruff	0.16.1	0.16.2
pytest-testcontainers	0.3.1	0.3.2
pytest-testcontainers-django	0.3.1	0.3.2
django-run-site	0.20.1	0.20.2
django-dev-helpers	0.1.14	0.2.0

Updates django-polish-inflection from 0.1.0 to 0.1.1

Commits

• 668eda5 release: 0.1.1
• cfe681a Merge pull request #1 from iplweb/feat/django-61
• 7d4891a feat: add Django 6.1 to the supported version matrix
• 6e6e8a0 chore: dodaj URL Funding do pyproject.toml
• 6fd8f0e chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-denorm-iplweb from 1.12.2 to 1.14.0

Changelog

Sourced from django-denorm-iplweb's changelog.

1.14.0 (2026-08-07)

This is a MINOR release rather than a patch: aggregates over a ManyToManyField are documented but have never actually worked on any release of this package, so making them work adds a capability instead of merely correcting a regression.

• CountField / SumField declared over a ManyToManyField now work. AggregateDenorm.m2m_triggers() — the through-table triggers, the only ones that see a row being added to or removed from an m2m relation — was reached exclusively from that configuration, and it had been dead since Django 1.8: get_related_where() called manager.related (gone), Query.add_count_column() (removed in 1.8) and clear_ordering(force_empty=True) (renamed in 4.0), so building the triggers raised AttributeError at denorm_init / install_triggers() time — every attempt failed, on every supported Django. The subquery is now built with the current Query API (add_annotation(Count("*"), ...), clear_ordering(force=True)). SumDenorm's related increment/decrement additionally selected self.fieldname — the denormalized column, which lives on the other model — instead of the summed column self.sum_field.
• The m2m through-table subquery is now compiled with the NEW / OLD quoting exemption introduced in 1.13.0, so the revived code path cannot reintroduce the Django 6.1 alias-quoting breakage. The exemption is now a mixin (TriggerAliasQuotingMixin) applied on top of whichever compiler class the backend hands out, rather than a hardcoded SQLCompiler subclass.

1.13.0 (2026-08-07)

• Added support for Django 6.1. CI now tests Django 5.2, 6.0 and 6.1; Django 6.1 (like 6.0) requires Python 3.12+.
• fix: Django 6.1 compatibility — filtered aggregates (CountField/SumField with filter=/exclude=) generated broken trigger DDL. Django 6.1 changed Col.as_sql() to use SQLCompiler.quote_name() instead of the now-deprecated quote_name_unless_alias(), so the fake NEW / OLD alias used to compile the filter came out as "NEW"."col" — a table reference, which PostgreSQL rejects with missing FROM-clause entry for table "NEW". The new TriggerSQLCompiler keeps those two PL/pgSQL record variables unquoted on every supported Django version.
• fix: Trigger.sql() now quotes the table name in the generated CREATE TRIGGER ... ON <table> / DROP TRIGGER ... ON <table> DDL. It was the one identifier in the trigger generator still interpolated raw (every TriggerAction* body already quoted its table), so a model with a reserved-word or mixed-case db_table produced broken trigger DDL at denorm_init / denorm_rebuild_triggers time.
• fix: the M2M CacheKeyField trigger now quotes the primary-key column in

... (truncated)

Commits

• e154bfc release: 1.14.0
• f0b08a1 Merge pull request #16 from mpasternak/fix/aggregate-m2m-dead-code
• 4ddb9a3 fix(aggregate): repair dead M2M code path using removed Query API
• 42ede6f release: 1.13.0
• a188610 Merge pull request #15 from mpasternak/feat/django-61
• 3e35fb6 feat: add Django 6.1 to the supported version matrix
• c7290b0 chore: dodaj URL Funding do pyproject.toml
• 5504633 chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-flexible-reports from 0.4.1 to 0.4.2

Release notes

Sourced from django-flexible-reports's releases.

v0.4.2

• Added support for Django 6.1. It joins 5.2 LTS and 6.0 in the tested matrix, on Python 3.12–3.14 (Django 6.1 requires Python 3.12+).

• Fixed validation of a Column whose Attribute name walks a relation in dot notation (parent.title) under Django 6.1. Resolving the far end of the relation went through the descriptor's get_queryset(), which in Django 6.1 takes a mandatory instance argument and so cannot be called off the model class any more; every such column was rejected as invalid. The related model now comes from the relation metadata, which reads the same on 5.2, 6.0 and 6.1.

Changelog

Sourced from django-flexible-reports's changelog.

0.4.2 (2026-08-07)

• Added support for Django 6.1. It joins 5.2 LTS and 6.0 in the tested matrix, on Python 3.12–3.14 (Django 6.1 requires Python 3.12+).

• Fixed validation of a Column whose Attribute name walks a relation in dot notation (parent.title) under Django 6.1. Resolving the far end of the relation went through the descriptor's get_queryset(), which in Django 6.1 takes a mandatory instance argument and so cannot be called off the model class any more; every such column was rejected as invalid. The related model now comes from the relation metadata, which reads the same on 5.2, 6.0 and 6.1.

Commits

• 6d9e96c release: 0.4.2
• 97c53ae Merge pull request #13 from mpasternak/feat/django-61
• b2ab430 feat: add Django 6.1 to the supported version matrix
• af4e317 chore: dodaj URL Funding do pyproject.toml
• ad02330 chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-dsl from 0.1.14 to 0.1.15

Changelog

Sourced from django-dsl's changelog.

0.1.15 (2026-08-07) +++++++++++++++++++

• Added support for Django 6.0 and Django 6.1 (both require Python 3.12 or newer).

Commits

• d758ba8 release: 0.1.15
• ad542fa Merge pull request #3 from mpasternak/feat/django-61
• abb51e4 fix(ci): preserve the pinned Django version by running tests with --no-sync
• 2669137 feat: add Django 6.0 and 6.1 to the supported version matrix
• 277a3d9 chore: dodaj URL Funding do pyproject.toml
• 3659431 chore: dodaj link BuyMeACoffee do FUNDING.yml
• dd2d7e4 Merge pull request #2 from mpasternak/fix/dsl-no-autoescape
• See full diff in compare view

Updates django-dynamic-admin-columns from 0.5.0 to 0.6.0

Changelog

Sourced from django-dynamic-admin-columns's changelog.

[0.6.0] - 2026-08-07

Added

• Support for Django 6.1. The CI matrix now covers Django 6.1 alongside 5.2 LTS and 6.0, and the trove classifiers advertise it. Django 6.1 requires Python 3.12+, so the 3.11 × 6.1 cell is excluded from the matrix just like 3.11 × 6.0.

• Tests for the package's own admin classes. tests/test_own_admin.py renders the ModelAdmin and ModelAdminColumn changelists, the column change form and adminsortable2's drag-and-drop reordering endpoint. ModelAdminColumnAdmin mixes in adminsortable2.admin.SortableAdminMixin — the most Django-version- fragile surface in the package — and nothing exercised it before.

Fixed

• django-admin-sortable2 floor raised from >=2.1 to >=2.1.2. Releases 2.1 and 2.1.1 returned pathlib.Path objects from SortableAdminMixin.change_list_template. Django's template loaders tolerated that through 5.2, but on Django 6.0 and 6.1 the lookup no longer resolves, so every sortable changelist — including this package's own ModelAdminColumn admin — raised TypeError: sequence item 0: expected str instance, PosixPath found while building the TemplateDoesNotExist message. 2.1.2 wraps the names in str(). Verified locally against Django 5.2, 6.0 and 6.1 at both the new floor and the current 2.3.1.

Commits

• 3485753 release: 0.6.0
• a9b0512 Merge pull request #2 from iplweb/feat/django-61
• 2e813e9 fix: raise django-admin-sortable2 floor to 2.1.2 for Django 6.x
• 4f1de96 chore: reformat the README example with current ruff
• 792a898 feat: add Django 6.1 to the supported version matrix
• e5012e6 chore: dodaj URL Funding do pyproject.toml
• 5a3964e chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-password-policies-iplweb from 0.9.0 to 0.9.4

Release notes

Sourced from django-password-policies-iplweb's releases.

0.9.4

Models

PasswordHistory and PasswordProfile gained __str__(), completing the work started for PasswordChangeRequired in 0.9.2. Both used to render in the admin as PasswordHistory object (1). History entries also carry their creation date, since a user has many of them and the username alone does not tell two rows apart. Written with gettext so they stay translatable.

URLs

password_policies.urls drops the Django 1.x compatibility shims and uses path() for the five static routes. The password reset confirmation route stays a re_path() — it passes three components positionally with length constraints that path() converters cannot express.

The published URLs are unchanged, and are now pinned by tests. Previously the whole suite reached its views through reverse(), which would have followed a route that silently changed shape.

A lint job that had never linted

The Lint job in CI was broken three independent ways at once, any one of which was enough to make it meaningless:

1. ruff was never declared as a dependency, so uv run ruff failed with Failed to spawn.
2. Both steps ended in || true, which hid that failure.
3. pyproject.toml listed W503 under ignore — a flake8 code ruff does not implement, and an unknown selector makes ruff abort before checking a single file.

It had been reporting success since it was added. All three are fixed; ruff now ships pinned in the dev extra and the job gates. It immediately caught nine real violations, including an unused import in views.py and dead locals in the Sphinx extension where a documented "fallback if there isn't any help text" had never actually been written.

Documentation

Now published at https://iplweb.github.io/django-password-policies-iplweb/, rebuilt from develop on every push. The previous Pages site had been serving a build from October 2016. The settings reference had also been rendering empty for years — it pointed autodoc at a password_policies.conf.Settings class that has never existed; it now documents all 30 settings. Sphinx runs with -W, so doc rot fails CI instead of quietly publishing a page with a hole in it.

Packaging

PyPI uploads move to Trusted Publishing (OIDC) — no long-lived API token is stored anywhere.

---

Thanks to @​mikemanger, whose #39 first pointed at the model, URL and lint threads, and to @​dragondive for the PasswordChangeRequired.__str__ work in 0.9.2.

Full changelog: https://github.com/iplweb/django-password-policies-iplweb/blob/v0.9.4/HISTORY.rst

v0.9.3

Fixed

• The password_status context processor no longer raises AttributeError when request carries no user.

  request.user only exists once AuthenticationMiddleware has run. It is missing while Django renders the 500 page for an exception raised earlier in the middleware chain — where the crash masked the very exception being handled — and whenever a template is rendered outside the request/response cycle (RequestFactory, e-mail rendering, management commands, Celery tasks). The processor now returns an empty context instead, the same way Django guards django.contrib.auth.context_processors.auth.

  Reported and diagnosed by @​kostrom (#21), fixed in #50.

Docs

• Sphinx documentation is now published at https://iplweb.github.io/django-password-policies-iplweb/, rebuilt from develop on every push, and linked from the README (#51).

Full changelog: iplweb/django-password-policies-iplweb@v0.9.2...v0.9.3

Changelog

Sourced from django-password-policies-iplweb's changelog.

0.9.4

• Add __str__ methods to the PasswordHistory and PasswordProfile models, completing the work started for PasswordChangeRequired in 0.9.2. History entries and profiles rendered in the admin as PasswordHistory object (1); they now name the user, and history entries also carry their creation date, since a user has many of them.

• Drop the Django 1.x compatibility shims from password_policies.urls and use path() for the five static routes. The password reset confirmation route stays a re_path() — it passes its three components positionally and constrains their length, which path() converters cannot express. The published URLs are unchanged and are now pinned by tests.

• Fix the ruff configuration. W503 was carried over from the old flake8 config, but ruff has no such rule, and an unknown selector makes ruff abort before checking anything. The lint job in CI had therefore never linted a single line — and ruff was never declared as a dependency either, so uv run ruff could not find it to begin with. Nine real violations the job had been hiding are fixed, ruff now ships pinned in the dev extra, and the job no longer swallows its own exit code.

  Thanks to @mikemanger <https://github.com/mikemanger>, whose [#39](https://github.com/iplweb/django-password-policies-iplweb/issues/39) <https://github.com/iplweb/django-password-policies-iplweb/pull/39> first pointed at all three of these.

• Publish to PyPI through Trusted Publishing (OIDC) instead of uploading by hand with a long-lived API token ([#53](https://github.com/iplweb/django-password-policies-iplweb/issues/53) <https://github.com/iplweb/django-password-policies-iplweb/pull/53>_).

• Record the tree-wide ruff format commit in .git-blame-ignore-revs so git blame — and GitHub's blame view, which reads the file automatically — skips over it ([#55](https://github.com/iplweb/django-password-policies-iplweb/issues/55) <https://github.com/iplweb/django-password-policies-iplweb/pull/55>_).

0.9.3

• Fix the password_status context processor raising AttributeError when request carries no user. This happens while Django renders the 500 page for an exception raised before AuthenticationMiddleware ran, and whenever a template is rendered outside the request/response cycle (RequestFactory, e-mails, management commands) — in the first case the crash masked the very exception being handled. The processor now returns an empty context instead, the same way Django guards django.contrib.auth.context_processors.auth. Thanks to @kostrom <https://github.com/kostrom>_ for reporting and diagnosing it ([#21](https://github.com/iplweb/django-password-policies-iplweb/issues/21) <https://github.com/iplweb/django-password-policies-iplweb/pull/21>_).
• Publish the Sphinx documentation to GitHub Pages at https://iplweb.github.io/django-password-policies-iplweb/, rebuilt from develop on every push, and link it from the README ([#51](https://github.com/iplweb/django-password-policies-iplweb/issues/51) <https://github.com/iplweb/django-password-policies-iplweb/pull/51>_).

0.9.2

... (truncated)

Commits

• 8ab32ff release: 0.9.4
• 09283c8 Merge pull request #55 from iplweb/ci/enforce-ruff
• 1bab48b chore: ignore the reformat commit in git blame
• 84efc8b Merge pull request #53 from iplweb/feat/pypi-trusted-publishing
• 939340b Merge pull request #54 from iplweb/feat/pr39-followup
• e526e44 build: declare ruff as a dev dependency
• 25ca842 style: format the repository with ruff and let the lint job fail
• ae2d71b feat: finish the model str methods, modernise urls.py, un-break ruff
• 506d596 ci: publish to PyPI via Trusted Publishing (OIDC)
• 61b702c Merge pull request #52 from iplweb/fix/docs-version-from-tags
• Additional commits viewable in compare view

Updates django-multiseek from 0.10.2 to 0.10.3

Changelog

Sourced from django-multiseek's changelog.

0.10.3

• Add support for Django 6.1 (Python 3.12+ only), tested in CI alongside 4.2, 5.1, 5.2 and 6.0. Declare the per-series Framework :: Django :: X.Y classifiers that were missing from pyproject.toml.
• CI matrix fixes: exclude Python 3.10/3.11 from the Django 6.x rows (Django 6.x requires Python >= 3.12); run the suite with uv run --no-sync so the resync no longer undoes the pinned Django version; pin pytest-django<4.13 for the 4.2 / 5.1 rows, since newer pytest-django dropped Django < 5.2.
• Fix the formatting of a code block in docs/IMPROVEMENTS.md (ruff 0.16 formats Markdown).

Commits

• 6a06e1e release: 0.10.3
• 272b7c2 Merge pull request #17 from mpasternak/feat/django-61
• f1f0527 fix(ci): keep the legacy Django cells green and satisfy ruff format
• 2eae4bc fix(ci): preserve the pinned Django version by running tests with --no-sync
• 3a73fbe feat: add Django 6.1 to the supported version matrix
• 6655d22 chore: dodaj URL Funding do pyproject.toml
• 0c3be04 chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-redis-iplweb from 6.0.1 to 6.0.2

Commits

• See full diff in compare view

Updates djangorestframework from 3.17.2 to 3.18.0

Release notes

Sourced from djangorestframework's releases.

3.18.0

What's Changed

Breaking changes

• Drop support for Django 4.2, Django 5.0 and Django 5.1 by @​p-r-a-v-i-n in encode/django-rest-framework#9899
• Change errors for list serializers (many=True) to dict format by @​p-r-a-v-i-n in encode/django-rest-framework#9837

Features

• Add unaccent to SearchFilter by @​mgaligniana in encode/django-rest-framework#9385
• Add support for Django 6.1 by @​browniebroke in encode/django-rest-framework#10003
• Add @throttle_scope function based view decorator by @​d-ryzhykau in encode/django-rest-framework#9963
• Add nulls_distinct support to UniqueTogetherValidator by @​mag123c in encode/django-rest-framework#9866

Bug fixes

• Include choices param for non-editable fields by @​ticosax in encode/django-rest-framework#9929
• Improve cursor pagination template accessibility in browsable API by @​kosbemrunal in encode/django-rest-framework#9905
• Fix partial form data updates involving ListField by @​Natgho in encode/django-rest-framework#9902
• Fix crash due to browsable API extra action permissions by @​dlfoerster in encode/django-rest-framework#9934
• Handle unhashable BooleanField representation value by @​emfpdlzj in encode/django-rest-framework#9973
• Fix OpenAPI schema for zero numeric bounds on ListField children by @​zainnadeem786 in encode/django-rest-framework#9977
• Replace cc_delim_re usage with split_header_value for Django 6.1+ compatibility by @​laymonage in encode/django-rest-framework#9978
• Fix set_rollback to only rollback initialized connections by @​jdetaeye in encode/django-rest-framework#9599
• Fix DictField HTML input returning empty dict for missing fields by @​veeceey in encode/django-rest-framework#9891
• Raise clear error for unsupported unique-together list updates by @​zainnadeem786 in encode/django-rest-framework#9981

Other changes

• Prepare release 3.18.0 by @​github-actions[bot] in encode/django-rest-framework#10015

New Contributors

• @​Im-Bilal made their first contribution in encode/django-rest-framework#9967
• @​dlfoerster made their first contribution in encode/django-rest-framework#9934
• @​emfpdlzj made their first contribution in encode/django-rest-framework#9973
• @​zainnadeem786 made their first contribution in encode/django-rest-framework#9977
• @​laymonage made their first contribution in encode/django-rest-framework#9978
• @​harshitkandpal made their first contribution in encode/django-rest-framework#9993
• @​udit-prabhakar made their first contribution in encode/django-rest-framework#9962
• @​sai09111995 made their first contribution in encode/django-rest-framework#9884
• @​d-ryzhykau made their first contribution in encode/django-rest-framework#9963
• @​Elkasitu made their first contribution in encode/django-rest-framework#8494
• @​vishalanandl177 made their first contribution in encode/django-rest-framework#10002
• @​jdetaeye made their first contribution in encode/django-rest-framework#9599
• @​veeceey made their first contribution in encode/django-rest-framework#9891
• @​mag123c made their first contribution in encode/django-rest-framework#9866
• @​anurag12anu made their first contribution in encode/django-rest-framework#9814
• @​github-actions[bot] made their first contribution in encode/django-rest-framework#10015

Full Changelog: encode/django-rest-framework@3.17.1...3.18.0

Commits

• 11875a3 Prepare release 3.18.0 (#10015)
• d346a8c Add note about Browsable API simulating POST in documentation (#9814)
• 80d535d Fix GHA workflow for preparing release
• aa1876b Update fields.md explaining how the source argument affects `.validated_dat...
• 000bb33 Add nulls_distinct support to UniqueTogetherValidator (#9866)
• 7508e0c Raise clear error for unsupported list update validation (#9981)
• 69d1cd7 Fix DictField HTML input returning empty dict for missing fields (#9891)
• bbc62ac Update Django 6.1 dependency to stable release. (#10016)
• f780434 Add GHA workflow to prepare a release
• dc027d2 set_rollback should only rollback initialized connections (#9599)
• Additional commits viewable in compare view

Updates djangoql-iplweb from 0.31.1 to 0.31.2

Changelog

Sourced from djangoql-iplweb's changelog.

0.31.2 (2026-08-07)

• Added support for Django 6.1 (Python 3.12--3.14). Django 6.1 is now part of the CI test matrix alongside 5.2 LTS and 6.0, and is advertised in the package classifiers. No code changes were required.

• Fixed the tests-postgres CI job, which silently ran against SQLite. The fixture swapped settings.DATABASES, but the default connection had already been materialised during django.setup(), so every "PostgreSQL" run actually exercised SQLite. The job now asserts hard on connection.settings_dict['ENGINE'] and additionally asks the server itself via SELECT version(). Four tests that had been overfitted to SQLite's SQL rendering (UPPER(...) LIKE and the time-zone offset handling) were corrected to match PostgreSQL. Tests and CI only -- no changes to the packaged code.

0.31.0 (2026-07-11)

• LLM schema — dictionary value deduplication (breaking JSON shape): a related model that is the target of several relations (a shared dictionary / lookup table -- e.g. many jezyk foreign keys, or a self-relation plus reverse relations) previously had its full value list re-emitted inline at every relation, wasting large amounts of prompt space on pure redundancy. Its values are now emitted once, in a new top-level dictionaries block keyed by (related_model, match_field), and each relation carries only a lightweight match_field / match_fields reference into it. str(obj) examples are deduplicated the same way under the "__str__" key.

  Breaking change to the JSON output shape: relation field entries no longer carry an inline related_values / related_examples value; instead they carry match_field (which may be "__str__") or match_fields, and the values live under dictionaries[relates_to][match_key]. Consumers that parsed per-field related_values must read from the top-level dictionaries block instead. The compact format changes correspondingly: a relation renders as -> model match <field> (or examples) with the values listed once in a dictionaries (...) block at the bottom, rather than inline match <field> in (...) at each relation. Semantics are otherwise unchanged -- fk_options, max_fk_options, no_value_targets, the auto-mode sensitive-target guard, and choices all behave exactly as before. As a side effect, a shared dictionary is now queried once rather than once per referencing relation.

0.30.3 (2026-07-10)

• LLM schema privacy — no_value_targets: new optional schema attribute,

... (truncated)

Commits

• 3ad9ca4 release: 0.31.2
• 17db804 Merge pull request #17 from iplweb/feat/django-61
• e48c233 feat: add Django 6.1 to the supported version matrix
• d3220ff Merge pull request #18 from iplweb/fix/postgres-job-actually-uses-sqlite
• 4e3a9d5 fix(tests): make the postgres job actually run against postgres
• 7364d03 chore: dodaj URL Funding do pyproject.toml
• 44d2e04 chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-dbtemplates-iplweb from 4.4.0 to 4.4.1

Changelog

Sourced from django-dbtemplates-iplweb's changelog.

v4.4.1 (2026-08-07)

• Added Django 6.1 to the supported version matrix (tox envlist and the Framework :: Django :: 6.1 trove classifier). Django 6.1 requires Python 3.12 or newer.

v4.4 (2026-07-04)

• Added the opt-in DBTEMPLATES_SKIP_UNKNOWN_NAMES setting. When enabled, the loader keeps an in-process set of the template names that exist in the database and skips the cache/DB lookup for any other name. This removes the hundreds of redundant django_template queries (or cache round-trips) that a Django-admin page otherwise triggers when only a few templates are stored in the database. Companion setting DBTEMPLATES_KNOWN_NAMES_TTL bounds the staleness window in multi-process deployments. Off by default; existing behaviour is unchanged. See :ref:Skipping unknown template names <skip_unknown_names>.

v5.0 (unreleased)

.. warning::

This is a backwards-incompatible release!

• Dropped support for Python 3.7 and Django < 4.2.

• Added support for Python 3.11, 3.12, 3.13.

• Django 5.x support

• Added support for Django 6.0 and 6.1 (both require Python 3.12 or newer).

v4.0 (2022-09-3)

.. warning::

This is a backwards-incompatible release!

• Dropped support for Python 2.7 and Django < 3.2.

• Added support for Python 3.8, 3.9, 3.10.

• Moved test runner to GitHub Actions:

  http://github.com/jazzband/django-dbtemplates/actions

... (truncated)

Commits

• b5b6cf4 docs: changelog entry for 4.4.1 (Django 6.1 support)
• 2247eae Merge pull request #2 from mpasternak/feat/django-61
• bec0873 feat: add Django 6.1 to the supported version matrix
• 22eb965 chore: dodaj URL Funding do pyproject.toml
• 945cf42 chore: dodaj link BuyMeACoffee do FUNDING.yml
• See full diff in compare view

Updates django-channels-broadcast from 0.2.2 to 0.3.0

Changelog

Sourced from django-channels-broadcast's changelog.

[0.3.0] - 2026-08-07

Released as a MINOR, not a patch: the return values of the public API change. The send_to_* / redirect_* / progress_* family is re-exported from channels_broadcast/__init__.py and listed in __all__, and until now it returned None both on success and on a flag-disabled no-op. Success now yields an explicit truthy sentinel, so code shaped like if send_to_user(...): ... — previously always false — starts behaving correctly. The documented contract ("no-op ⇒ None") is unchanged; it simply became true.

Fixed

• send_notification no longer prints No-op: the relevant CHANNELS_BROADCAST_ENABLE_* flag is False … after a message that was actually delivered. The command inferred "no-op" from a None return value, but channel_layer.group_send() / .send() return None on success — so every single invocation looked like a no-op, for every audience and every kind.

Changed

• Every send_to_* / redirect_* / progress_* function in channels_broadcast.api now returns True once the payload has been handed to the channel layer, and None (unchanged) when the relevant CHANNELS_BROADCAST_ENABLE_* flag made it a no-op. Previously they forwarded the channel layer's own return value, which is None regardless of outcome. The documented contract ("no-op returns None") is unchanged — it just became true.
• send_notification now confirms a successful dispatch with a Sent: --audience=…, --kind=… line on stdout.

[0.2.3] - 2026-08-07

Added

• Support for Django 6.1 (tested in CI on Python 3.12 and 3.13; Django 6.1 requires Python ≥ 3.12).

[0.2.1] - 2026-06-18

Fixed

• notifications.js no longer emits a useless ?extraChannels= query param when there are no channels to subscribe to. normalizeExtraChannels now returns null (→ param omitted) for an empty array, the already-JSON strings "[]", '""' and "null", and whitespace-only input. The '""' case is the common Django footgun where {{ extraChannels|json_script }} on an undefined context variable renders json.dumps('') === '""', which used to leak as ?extraChannels=%22%22. Non-empty arrays and non-JSON

... (truncated)

Commits

• See full diff in compare view

Updates django-countdown from 0.3.0 to 0.3.1

Changelog

Sourced from django-countdown's changelog.

[0.3.1] — 2026-08-07

A metadata-only release: no source changes, just the declared support for Django 6.1 plus the CI and packaging fixes listed below.

Added

• Support for Django 6.1, released 2026-08-05. The CI matrix gains Django 6.1 on Python 3.12, 3.13 and 3.14 — 6.1 requires Python 3.12 or newer, so the 3.10/3.11 cells stay 5.2-only. No source changes were needed; the Framework :: Django :: 6.1 trove classifier is declared.

Changed

• Trove classifier moved from Development Status :: 3 - Alpha to 4 - Beta. The command set now covers the whole countdown lifecycle, tests run across Python 3.10–3.14 × Django 5.2/6.0/6.1, and the documented behaviour is under test — the API is stable enough to depend on. Takes effect on PyPI with the next release; 0.3.0 shipped as Alpha.

Fixed

• CI actions bumped off Node 20, which GitHub has deprecated: actions/checkout@v5, upload-artifact@v7, download-artifact@v8, deploy-pages@v5, setup-uv v9. Note that upload-artifact@v5 and download-artifact@v5 are still Node 20 — the jump to v7/v8 is what actually moves them.
• setup-uv's cache key was never invalidated: it globs for uv.lock, which this repository gitignores (a library pins nothing), so the file never reached the runner and nothing ever matched. Keyed on pyproject.toml instead, with a per-job cache-suffix. The suffix is not cosmetic: setup-uv runs before uv python install, so its key carries the runner's Python rather than the matrix one, and all eight matrix jobs would otherwise compute an identical key and race to reserve it.

Commits

• bdc7386 release: 0.3.1
• f91b78d Merge pull request #3 from iplweb/feat/django-61
• 296a315 fix(ci): preserve the pinned Django version by running tests with --no-sync
• 14beb01 feat: add Django 6.1 to the supported version matrix
• b0f1276 Merge pull request #2 from iplweb/chore/ci-cache-suffix
• 62e79b2 chore(ci): rozdziel klucze cache miedzy zadania macierzy
• fe84b48 Merge pull request #1 from iplweb/chore/actions-node24-and-beta
• 3c5bac8 chore(ci): przenies akcje na Node 24, napraw cache uv, oznacz jako beta
• See full diff in compare view

Updates django-formdefaults from 0.6.2 to 0.6.3

Changelog

Sourced from django-formdefaults's changelog.

[0.6.3] — 2026-08-07

Added

• Support for Django 6.1 (released 2026-08-05). CI now runs the suite against Django 6.1 on Python 3.12 and 3.13, and the package advertises the Framework :: Django :: 6.1 classifier.
• Django 6.0 promoted from an experimental pre-release job to a regular, blocking CI target now that 6.0 is stable. The Framework :: Django :: 6.0 classifier ships publicly for the first time with this release — the metadata on PyPI previously stopped at 5.2.
• A non-blocking CI job that installs Django from its development branch (main, currently 6.2.dev), so upcoming deprecations surface early without failing pull requests.

Fixed

• CI now installs pytest-django<4.13 for the Django 4.2, 5.0 and 5.1 targets. pytest-django 4.13 dropped support for Django below 5.2 without declaring a version floor, so those seven jobs errored out at fixture setup (SimpleTestCase._pre_setup_ran_eagerly does not exist before Django 5.2). The package itself is unaffected — the whole suite passes on 4.2, 5.0 and 5.1 once the test runner is paired correctly.

Removed

• Python 3.10 from the CI matrix, the README support table and the trove classifiers. The package has declared requires-python = ">=3.11" since 0.6.0, so the 3.10 jobs could never install it and were failing on every run.

Commits

• 4c354f5 chore: release 0.6.3
• 1ce4d8a Merge pull request #1 from iplweb/feat/django-61
• c55098e ci: hold pytest-django below 4.13 for Django 4.2/5.0/5.1
• 2d04d9b feat: add Django 6.1 to the supported version matrix
• 500ab1c chore: dodaj URL Funding do pyproject.toml
• 1d36019 chore: dodaj link BuyMeACoffee do FUNDING.yml
• 73b497d docs(claude): expand CLAUDE.md per /init — architecture, models, commands
• e9a4039 docs: add CLAUDE.md with i18n isolation rule, release workflow, repo layout
• See full diff in compare view

Updates django-pg-baseline from 0.3.0 to 0.3.1

Changelog

Sourced from django-pg-baseline's changelog.

[0.3.1] - 2026-08-07

Added

• Support for Django 6.1. Added to the CI matrix (Python 3.12 / 3.13 only — Django 6.x requires Python >= 3.12) and to the PyPI classifiers. No source changes were needed.

Fixed

• Version metadata drift: pyproject.toml declared 0.2.0 and django_pg_baseline.__version__ declared 0.1.0, while 0.3.0 was already published on PyPI. Both now read 0.3.1 and match the released artifact.

[0.2.0] - 2026-05-09

Added

• baseline_update management command and rebuild.update_baseline() function. Loads the existing baseline.sql into the testcontainer before migrate, so Django's post_migrate preserves existing auto-increment IDs (permission / content_type rows) via get_or_create. Routine refreshes after adding migrations now produce minimal git diffs instead of ~1500–2000-line churn from auth/contenttype ID drift. See README for the baseline_rebuild vs baseline_update workflow.
• rebuild._load_baseline_into_container() helper — streams a SQL file into the testcontainer's PG via docker exec -i ... psql.

[0.1.0] - 2026-05-08

Added

• Initial extraction from BPP (bpp/src/django_pg_baseline/).
• BaselineConfig typed loader for settings.PG_BASELINE.
• loader.load_baseline() — stdlib-only psql shell-out.
• loader.baseline_needed() — to_regclass('public.django_migrations') probe.
• patches....

  Description has been truncated

[mpasternak]

Zastąpione przez #759 (zmergowane jako 44e5f7d) — 21 z 22 aktualizacji wjechało bez zmian.

Wyjątkiem jest django-pg-baseline, które zostaje na 0.3.0. Wersja 0.3.1 usuwa komendę baseline_check, przez co job baseline-check w .github/workflows/tests.yml padał tutaj z Unknown command: 'baseline_check'. Pozostałe baseline_info jest czysto informacyjne (zawsze exit 0), więc nie zastąpi bramki — podniesienie tej zależności bez przepisania joba zamieniłoby realny gate w dekorację.

W #759 pin jest jawny (>=0.3.0,<0.3.1) z uzasadnieniem w pyproject.toml. Migracja na 0.3.1 do zrobienia osobno: API django_pg_baseline.freshness.check_freshness nadal istnieje.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml