Update supported versions to reflect state of the world and declare new version #5
Conversation
This file contains 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
lirsacc-mns
changed the title
|
@PeterJCLaw It looks like CI is setup and _should ™️ _ auto release on merge but I don't seem to have access (even with my personal already in the thread org account) so I can't check this or fix it if anything goes wrong. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
<5qualifier is preventing users from upgrading to Django 5.This relaxes the constraint to
<6and generally reflects the state of the world with upward versions and deprecated Python versions.Not making it a breaking major as I don't think dropping out of support python versions counts (otherwise we're doing a major a year for everything by definition).