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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github.com/ProtonMail/go-crypto from 1.1.2 to 1.1.3 #682

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 25, 2024

Bumps github.com/ProtonMail/go-crypto from 1.1.2 to 1.1.3.

Release notes

Sourced from github.com/ProtonMail/go-crypto's releases.

v1.1.3

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.2...v1.1.3

Release v1.1.3-proton

What's Changed

This release is v1.1.3 with support for the following non-standardized features:

Commits
  • 5521d83 Flag to allow signing key decryption (#251)
  • 5e3e39d Improve error message for decryption with a session key (#237)
  • 33a08b3 Merge pull request #247 from ProtonMail/improve-aead
  • 9ad5572 Adapt aead preferences on key generation (#248)
  • 531d9f5 Improve documentation
  • 1efe4a0 Deprecate SerializeEncryptedKey[WithHiddenOption] and SerializeSymmetricKeyEn...
  • ee67844 Add SerializeSymmetricKeyEncryptedAEADReuseKey
  • 63e3da1 [v2] Use AEAD if all public keys support it
  • d7733dc Validate argon2 params on read (#246)
  • c0ca2b8 Add argon2 test vector for 32-bit platforms (#245)
  • See full diff in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.1.2 to 1.1.3.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.2...v1.1.3)

---
updated-dependencies:
- dependency-name: github.com/ProtonMail/go-crypto
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Nov 25, 2024
@mergify mergify bot merged commit 3433ea1 into master Nov 25, 2024
5 checks passed
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.3 branch November 25, 2024 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants