Skip to content

Closes #8032: Upgrade to Django 4.0 #8510

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

Merged
merged 5 commits into from
Feb 7, 2022
Merged

Closes #8032: Upgrade to Django 4.0 #8510

merged 5 commits into from
Feb 7, 2022

Conversation

jeremystretch
Copy link
Member

@jeremystretch jeremystretch commented Feb 1, 2022

Closes: #8032

NOTE: Because graphene-django does not yet support Django v4.0, this branch is currently using a fork which has added v4.0 support. Once the relevant PR has been merged, this will be returned to the normal package.

  • Bumps Django to 4.0
  • Tweak old migrations to avoid introducing no-op migrations
  • Remove dependency on private is_safe_url() function

@jeremystretch jeremystretch merged commit 733a9bb into feature Feb 7, 2022
@jeremystretch jeremystretch deleted the 8032-django-40 branch February 7, 2022 16:47
@jeremystretch
Copy link
Member Author

We're now pulling graphene-django from its v2 branch in anticipation of the v2.16 release (date TBD).

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant