You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent PR we were constrained in the update of this library by our then Django 2.2. As from pending now megred PR #2737 we have removed that constraint and cleared the way, in part, for our jump to Django 4.2 LTS.
Follow-up to: "Update Django REST Framework within Django version constraint #2695" #2697
Our current testing branch pyproject.toml has:
djangorestframework = "==3.13.1" # Last version to support Django 2.2 (up to 4.0)
Updates DRF from 3.13.1 to latest 3.14.0. Via removal of
our now redundant Django version related pinning.
# Includes
- Incidental urllib3 update from 2.0.7 to 2.1.0.
In a recent PR we were constrained in the update of this library by our then Django 2.2. As from
pendingnow megred PR #2737 we have removed that constraint and cleared the way, in part, for our jump to Django 4.2 LTS.Follow-up to: "Update Django REST Framework within Django version constraint #2695" #2697
Our current testing branch pyproject.toml has:
PyPi: https://pypi.org/project/djangorestframework/
Project Changelog: https://www.django-rest-framework.org/community/release-notes/#release-notes
Curiously we have there for the latest version:
However from the GitHub repo README.md 'requirements': https://github.com/encode/django-rest-framework#requirements
Presumably pertaining to master branch. So we may want to keep an eye out for 3.14.X versions as we approach Django 4.2.
Regarding the pending 3.15 release, with presumably official Django 4.2, we have the following upstream Milestone:
https://github.com/encode/django-rest-framework/milestone/78
It would seem that we may well be OK to use 3.14 for Django 4.2: from the two comments here in a pending 3.15 Milestone issue: encode/django-rest-framework#8794 (comment)
It seems from comment: encode/django-rest-framework#8942 (comment)
that we can use DRF 3.14 as long as we use at least Django 4.2.1.
The text was updated successfully, but these errors were encountered: