Skip to content

Update version compatibility metadata #2954

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

Open
intgr wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update version compatibility metadata #2954

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
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ We rely on different `django` and `mypy` versions:

| django-stubs | Mypy version | Django version | Django partial support | Python version |
|----------------|--------------|----------------|------------------------|----------------|
| (unreleased) | 1.13 - 1.19 | 5.2 | 6.0, 5.1, 5.0 | 3.10 - 3.14 |
Copy link
Member

@sobolevn sobolevn Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| (unreleased) | 1.13 - 1.19 | 5.2 | 6.0, 5.1, 5.0 | 3.10 - 3.14 |
| (unreleased) | 1.13 - 1.19 | 6.0 | 5.2, 5.1, 5.0 | 3.10 - 3.14 |

Copy link
Collaborator Author

@intgr intgr Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're still closer to 5.2 than we are to fully supporting 6.0, for now.

I'd like to make a release at one point, to put out the "announcement" #2944 to perhaps get more help from the community.

But it's also an option to make a release from a branch, excluding all 6.0 changes.

Copy link
Member

@sobolevn sobolevn Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be ideal to make a release with 5.2 and 3.14 as the last 5.2 release and then move on to 6.0 changes. And make the announcement. But, this will require a new branch with manual cherry-picking of commits.

| 5.2.8 | 1.13 - 1.19 | 5.2 | 5.1, 5.0 | 3.10 - 3.13 |
| 5.2.7 | 1.13 - 1.18 | 5.2 | 5.1, 5.0 | 3.10 - 3.13 |
| 5.2.6 | 1.13 - 1.18 | 5.2 | 5.1, 5.0 | 3.10 - 3.13 |
Expand Down
2 changes: 2 additions & 0 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,13 @@ classifiers = [
"Programming Language :: Python :: 3.11",
"Programming Language :: Python :: 3.12",
"Programming Language :: Python :: 3.13",
"Programming Language :: Python :: 3.14",
"Typing :: Typed",
"Framework :: Django",
"Framework :: Django :: 5.0",
"Framework :: Django :: 5.1",
"Framework :: Django :: 5.2",
"Framework :: Django :: 6.0",
]
dependencies = [
"django",
Expand Down
Loading