Skip to content

Conversation

@timgraham
Copy link
Collaborator

@timgraham timgraham commented Apr 5, 2025

Django 6.0 was released December 3, 2025.

@timgraham timgraham force-pushed the django60 branch 3 times, most recently from cffe090 to fa7c204 Compare April 9, 2025 16:11
@timgraham timgraham force-pushed the django60 branch 2 times, most recently from c9da5c5 to 44f6148 Compare May 22, 2025 20:18
@timgraham timgraham force-pushed the django60 branch 2 times, most recently from 2294362 to 882aaad Compare July 7, 2025 19:20
@timgraham timgraham force-pushed the django60 branch 2 times, most recently from 8641710 to b1e2da4 Compare September 18, 2025 17:55
@timgraham timgraham marked this pull request as ready for review December 3, 2025 19:47
@timgraham timgraham requested a review from rafiss December 4, 2025 14:13
@@ -1,14 +1,6 @@
# Changelog

## 5.2.1 - Unreleased
Copy link
Contributor

Choose a reason for hiding this comment

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

should we create a separate branch for Django 5.2 support, and make a release from there? (separately from this PR)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, there are stable branches in case we need to backport any critical fixes. I made the 5.2.1 release.

@timgraham timgraham merged commit abe294c into cockroachdb:master Dec 5, 2025
18 checks passed
@timgraham timgraham deleted the django60 branch December 5, 2025 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants