-
Notifications
You must be signed in to change notification settings - Fork 28
upgraded django to 4.2.16 #1264
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
Conversation
loganbertram
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Echoing Jim's note about too many cryptography .whl files. May be worth making sure that's all in line while we're here, even if it's not to the spirit of the ticket. Everything seems to work, but I'd check those extra files in the vendor dir and remove the errant /code/ part of the path generated by pip-compile and then we should be good!
requirements/requirements.dev.txt
Outdated
| --hash=sha256:6279836d581513a26f1bf235f9acd333bc9115683f14f7e8fae46c98fc50e015 | ||
| # via | ||
| # -r requirements/requirements.in | ||
| # -r /code/requirements/requirements.in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
potentially ran from the wrong directory? we shouldn't be updating these. it's not a huge deal except that it will unexpectedly flip flop if people run the commands in different ways.
loganbertram
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
JFU-NAVA-PBC
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM

JIRA Ticket:
BB2-3512
What Does This PR Do?
Upgrades Django versioning from 4.2.15 to 4.2.16
What Should Reviewers Watch For?
Any references to 4.2.15 and any possible hashes in the requirements.in file that are wrong.
Validation
Ran locally and checked major functionality like getting auth tokens.
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
security engineer's approval.
Any Migrations?
etc)