Skip to content

Conversation

@bwang-icf
Copy link
Contributor

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:

  • Adds any new software dependencies
  • Modifies any security controls
  • Adds new transmission or storage of data
  • Any other changes that could possibly affect security?
  • Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
    security engineer's approval.

Any Migrations?

  • Yes, there are migrations
    • The migrations should be run PRIOR to the code being deployed
    • The migrations should be run AFTER the code is deployed
    • There is a more complicated migration plan (downtime,
      etc)
  • No migrations

@JFU-NAVA-PBC
Copy link
Contributor

noticed that there are multiple whl files for cryptography lib:
image

only one is needed here...

Copy link
Contributor

@loganbertram loganbertram left a 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!

--hash=sha256:6279836d581513a26f1bf235f9acd333bc9115683f14f7e8fae46c98fc50e015
# via
# -r requirements/requirements.in
# -r /code/requirements/requirements.in
Copy link
Contributor

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.

Copy link
Contributor

@loganbertram loganbertram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Copy link
Contributor

@JFU-NAVA-PBC JFU-NAVA-PBC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bwang-icf bwang-icf merged commit aecfe03 into master Nov 14, 2024
6 checks passed
@bwang-icf bwang-icf deleted the brandon/BB2-3512-upgrade-django branch November 14, 2024 16:56
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.

4 participants