-
Notifications
You must be signed in to change notification settings - Fork 173
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
requirements: update django to 3.2 LTS #360
Conversation
fbaeac2
to
a1a7f0b
Compare
I am cautiously optimistic but unless mistaken, it seems like it just works ? |
Build failed.
|
c43bca4
to
73d1411
Compare
Should be OK now I think but it would need to be rebased on top of #361 once it merges due to an unrelated failing linter test. This is probably a significant enough change to warrant leaving it out of 1.5.8 (which is already long overdue) but it should otherwise be good to land. |
Build failed.
|
73d1411
to
1122cd4
Compare
Build succeeded.
|
recheck |
CI fixes have been done. Let's keep this for another version bump, it would be a good fit to include with the update from bootstrap 4 to bootstrap 5: #339 |
Just noticed, we shouldn't forget about updating the documentation links to point to django 3.2 instead of 2.2: https://raw.githubusercontent.com/ansible-community/ara/master/doc/source/api-configuration.rst
|
Build succeeded.
|
We've been recommending django 2.2 LTS and now that 3.2 has been out for almost a year, we should bump the requirement.
Build succeeded.
|
We've been recommending django 2.2 LTS and now that 3.2 has been out for
almost a year, we should bump the requirement.