-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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.
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
chore: Prepare develop-4 for Django CMS 4.2 #7913
Conversation
bae5d1b
to
88ba3de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done a chunk more. So this is like a "save your progress"
@@ -12,21 +12,15 @@ jobs: | |||
strategy: | |||
fail-fast: false | |||
matrix: | |||
python-version: [ 3.9, '3.10', '3.11', '3.12' ] # latest release minus two | |||
python-version: [3.9, '3.10', '3.11', '3.12',] # latest release minus two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just thinking about versions. Python 3.13 is in beta ahead of a launch in October and django 5.1 is in alpha ahead of August release.
Maybe easier in a new PR, which I might have a look at this morning. But feels like testing against upcoming versions needs adding.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's a great idea.
Description
This PR:
After merging this RP, bug fixes need to be backported to the
release/4.1.x
branch.Related resources
Checklist
develop-4