Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency cryptography to v2.9.2 #141

Merged
merged 1 commit into from
May 10, 2020
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 2, 2020

This PR contains the following updates:

Package Update Change
cryptography minor ==2.8 -> ==2.9.2

Release Notes

pyca/cryptography

v2.9.2

Compare Source

v2.9.1

Compare Source

v2.9

Compare Source


Renovate configuration

馃搮 Schedule: At any time (no schedule defined).

馃殾 Automerge: Disabled by config. Please merge this manually once you are satisfied.

鈾伙笍 Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

馃敃 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency cryptography to v2.9 Update dependency cryptography to v2.9.1 Apr 21, 2020
@renovate renovate bot force-pushed the renovate/cryptography-2.x branch 2 times, most recently from 159d34a to 13a880b Compare April 22, 2020 23:48
@renovate renovate bot changed the title Update dependency cryptography to v2.9.1 Update dependency cryptography to v2.9.2 Apr 22, 2020
@renovate renovate bot force-pushed the renovate/cryptography-2.x branch from 13a880b to 57049ff Compare May 10, 2020 01:53
@quvox quvox merged commit a5f09c1 into develop May 10, 2020
@quvox quvox deleted the renovate/cryptography-2.x branch May 10, 2020 02:02
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.

None yet

2 participants