🚧chore: Add support for Django 4.2 #131
Merged
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
fixed rsinger86#114 adopted some of the changes in rsinger86#115 and those in rsinger86/django-lifecycle@0.9.2...0.9.3 Signed-off-by: KimSia, Sim <245021+simkimsia@users.noreply.github.com>
|
@EnriqueSoria this is my attempt to bump the support for Django 4.2 which is my primary concern. Do let me know if there are any changes I need to make. Thank you |
|
Thank you @rsinger86 How do I help release the new version on pypi? |
|
Oh ignore my last statement @rsinger86 I just saw 1.0.2 Thank you |
Merged
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.
fixed #114
adopted some of the changes in #115
and those in 0.9.2...0.9.3
PS
After this is merged, the next PR i will likely make is to drop support for Django versions that are outdated. This will be everything before 3.2 and 4.0.