Skip to content

Conversation

@bwang-icf
Copy link
Contributor

JIRA Ticket:
BB2-3512

What Does This PR Do?

Adding in .16 whl file

What Should Reviewers Watch For?

Missing whl files/improper django versions

If you're reviewing this PR, please check for these things in particular:

Validation

spin up locally and test

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

local run failed:

Preparing metadata (setup.py): started
13.51 Preparing metadata (setup.py): finished with status 'done'
13.52 Processing ./vendor/urllib3-1.26.19-py2.py3-none-any.whl (from urllib3[socks]==1.26.19->-r requirements/requirements.dev.txt (line 844))
13.55 Processing ./vendor/voluptuous-0.13.1-py3-none-any.whl (from -r requirements/requirements.dev.txt (line 852))
13.57 ERROR: Could not find a version that satisfies the requirement werkzeug==3.0.6 (from versions: 3.0.3)
13.57 ERROR: No matching distribution found for werkzeug==3.0.6

@bwang-icf bwang-icf merged commit bc3004b into master Nov 21, 2024
6 checks passed
@bwang-icf bwang-icf deleted the adding_django_whl branch November 21, 2024 21:47
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