-
Notifications
You must be signed in to change notification settings - Fork 40
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
chore(deps): bump cryptography from 3.3.1 to 3.3.2 #393
Conversation
Bumps [cryptography](https://github.com/pyca/cryptography) from 3.3.1 to 3.3.2. - [Release notes](https://github.com/pyca/cryptography/releases) - [Changelog](https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst) - [Commits](pyca/cryptography@3.3.1...3.3.2) Signed-off-by: dependabot[bot] <[email protected]>
I'm able to download scenarios using this branch on mac os, should we merge or does anyone else want to try? |
If you can download them it means that you can establish the connection with the server using the RSA key so I would say it is fine. The question I have is should we update the Pipfile in this PR too? Only the lockfile is updated here. |
I'd say it's fine to only update the lock file, since |
I forgot about that. At some we had |
Apparently dependabot tried to create similar PRs in Pre/PostREISE since the lock files there contain powersimdata deps as well, but it didn't know how to handle the relative path we use, e.g. here. Could do manually if we want to, but don't think it's that urgent. |
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.
I confirm that this works to both get data from previous scenarios and to launch new ones.
Who will merge that. Should I do it? |
Thank you for volunteering. |
I am not responsible if it breaks everything |
Bumps cryptography from 3.3.1 to 3.3.2.
Changelog
Sourced from cryptography's changelog.
Commits
82b6ce2
correct buffer overflows cause by integer overflow in openssl (#5747)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.