build: bump cryptography from 50.0.0 to 50.0.1 in /requirements - #747
Open
blaipr wants to merge 1 commit into
Open
build: bump cryptography from 50.0.0 to 50.0.1 in /requirements#747blaipr wants to merge 1 commit into
blaipr wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SUMMARY
Bumps
cryptographyfrom50.0.0to50.0.1inrequirements/requirements.txt. It underpins the credential encryption and the TLS paths.The Python requirements are outside Dependabot's scope on purpose: #675 turned on version updates for github-actions and for npm in
/awx/uiand left this file out, because it is compiled byrequirements/updater.shrather than hand-pinned. So this was produced the same waymake requirementsproduces it:run inside the
ascender_develimage, which is where that script insists on running. The result is 1 added / 1 removed in the lockfile.ISSUE TYPE
COMPONENT NAME
ASCENDER VERSION
Tests
Tested before opening, in the same image, with
cryptography 50.0.1installed into the AWX venv:CI does not run on pull requests from a fork until a maintainer approves the workflow, so this is what stands behind the change until then.