Add Django 6.1 support - #3
Merged
Merged
Conversation
Django 6.1 was released 2026-08-05 and requires Python 3.12 or newer, so it joins the CI matrix on the same interpreters as 6.0 (3.12, 3.13, 3.14) and the 3.10/3.11 cells stay 5.2-only. The full suite passes on Django 6.1 with no source changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…o-sync
The test job pinned a Django series with `uv pip install "Django~=X.Y.0"` and then
invoked a bare `uv run`, which re-syncs the environment from the project metadata /
uv.lock before executing. That silently reinstalled a different Django and discarded
the pin, so every matrix cell ran the same version regardless of matrix.django-version.
Reproduced locally:
uv sync && uv pip install "Django~=5.2.0"
.venv/bin/python -c "import django; print(django.get_version())" # 5.2.17
uv run python -c "import django; print(django.get_version())" # 6.1 <- pin lost
uv run --no-sync python -c "import django; print(django.get_version())" # 5.2.17
Without this, adding Django 6.1 to the matrix would not have tested it.
Lint / example-check jobs are untouched: they do not pin Django.
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
1 participant
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.
Django 6.1 was released 2026-08-05. This adds it as a first-class test target.
Like 6.0, Django 6.1 requires Python >= 3.12, so the new matrix cells are 3.12, 3.13 and 3.14 only — the 3.10 and 3.11 rows stay 5.2-only. The matrix goes from 8 to 11 cells.
Changed
.github/workflows/tests.yml— new# Django 6.1block in theinclude:matrix with entries for Python 3.12, 3.13 and 3.14. The install step is untouched:uv pip install "django~=${DJANGO_VER}.0"resolves~=6.1.0to>=6.1.0,<6.2correctly.pyproject.toml— added theFramework :: Django :: 6.1trove classifier. The dependency isdjango>=5.2with no upper pin, so nothing had to be loosened.README.md,docs/index.md— supported-versions tables gain a 6.1 row; cell counts updated 8 → 11.docs/contributing.md— CI description updated to the 11-cell matrix.CHANGELOG.md—Addedentry under Unreleased.Notes
release.ymlruns the suite on Python 3.13 with whatever Djangouv syncresolves; that will pick up 6.1 on its own once released, no change needed.uv pip install -e ".[test]" "Django~=6.1.0"thenpytest→ 204 passed. No deprecation or API breakage surfaced, so no source changes were needed.🤖 Generated with Claude Code