CHORE: add Django 6.1 RC1 to CI test matrix - #543
Draft
bewithgaurav wants to merge 4 commits into
Draft
Conversation
Adds py{312,313,314}-django61 tox env (django>=6.1a1,<6.2 resolves to 6.1rc1)
and wires it into the Windows and Linux ADO matrices. Lifts the setup.py
install_requires cap to <6.2 so the package install doesn't downgrade Django
away from 6.1rc1 during tox. Exploratory: surfaces 6.1 breakage early.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Removes the django32/django40/django41 legs from the Windows and Linux ADO matrices and their tox envs/deps. These EOL/older lines just crowd every CI run. Lowest tested Django is now 4.2. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Django 6.1 defaults supports_on_delete_db_cascade / _db_null / _db_default to True in BaseDatabaseFeatures, which pushes ON DELETE actions down to the FK constraint. SQL Server rejects FK graphs with multiple cascade paths to the same table (error 1785), which Django's new delete-app test models trigger, crashing test-db creation before any 6.1 test runs. Override the three flags to False so Django falls back to ORM-level delete emulation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Temporary: comment out every matrix leg except Linux/Windows Python3.14 - Django 6.1 so we iterate fast on the 6.1 compat work with just 2 runs. Revert this commit to restore the full matrix. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
📊 Code Coverage Report
Diff CoverageDiff: dev...HEAD, staged and unstaged changesNo lines with coverage information in this diff. 📋 Files Needing Attention📉 Files with overall lowest coverage (click to expand)- mssql/client.py: 20.0% (40 lines)
- mssql/creation.py: 39.7% (73 lines)
- mssql/functions.py: 67.7% (427 lines)
- mssql/base.py: 68.4% (513 lines)
- mssql/compiler.py: 72.3% (639 lines)
- mssql/operations.py: 78.2% (395 lines)
- mssql/schema.py: 82.3% (718 lines)
- mssql/introspection.py: 82.8% (128 lines)
- mssql/features.py: 95.1% (82 lines)
- mssql/__init__.py: 100.0% (1 lines)🔗 Quick Links
|
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.
draft, exploratory only, not for merge yet. adds django 6.1rc1 to CI so we can see what breaks before 6.1 final ships and scope the work to keep the backend green.
what changed:
py{312,313,314}-django61pinned todjango>=6.1a1,<6.2, which resolves to 6.1rc1 todaysetup.pyinstall_requirescap to<6.2so the package install during tox doesn't downgrade django back off 6.1rc1no changes to
mssql/*. leaving as draft so no reviewers get pinged. once CI runs I will triage the failures into a punch list of what it takes to support 6.1.