Skip to content

Drop support for Django 3.2 #1219

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 1 commit into from
Apr 17, 2024

Conversation

sliverc
Copy link
Member

@sliverc sliverc commented Apr 17, 2024

Description of the Change

Run django-upgrade --target-version 4.2

Checklist

  • PR only contains one change (considered splitting up PR)
  • unit-test added
  • documentation updated
  • CHANGELOG.md updated (only for user relevant changes)
  • author name in AUTHORS

@sliverc sliverc requested a review from n2ygk April 17, 2024 20:30
Run django-upgrade --target-version 4.2
@n2ygk n2ygk force-pushed the drop_django_42_support branch from e92b37a to 4fbaf24 Compare April 17, 2024 20:48
@n2ygk
Copy link
Contributor

n2ygk commented Apr 17, 2024

codecov having performance problems: https://status.codecov.com/incidents/wxf45dcr5ysr so merging this

@n2ygk n2ygk merged commit fc0d0b5 into django-json-api:main Apr 17, 2024
10 checks passed
@sliverc sliverc deleted the drop_django_42_support branch April 18, 2024 10:30
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