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.0-alpha.2-proton to 1.1.0-alpha.3-proton #592

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 1, 2024

Bumps github.com/ProtonMail/go-crypto from 1.1.0-alpha.2-proton to 1.1.0-alpha.3-proton.

Release notes

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

v1.1.0-alpha.3-proton

This pre-release is v1.1.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

Commits
  • dfc5210 Fix HMAC generation (#204)
  • a0d3abb Replace ioutil.ReadAll with io.ReadAll
  • 12d80ee fix(v2): Adapt NewForwardingEntity to refactored NewEntity
  • 00db3be fix(v2): Do not allow encrpytion with a forwarding key
  • 49c1020 feat: Add symmetric keys to v2
  • bce9b31 fix: Address warnings
  • e202bef feat: Add forwarding to v2 api
  • 2a86d28 fix: Address rebase on version 2 issues
  • a425074 Use fingerprints instead of KeyIDs
  • b55bb97 Create a copy of the encrypted key when forwarding
  • Additional commits viewable 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.0-alpha.2-proton to 1.1.0-alpha.3-proton.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.0-alpha.2-proton...v1.1.0-alpha.3-proton)

---
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 Jul 1, 2024
@mergify mergify bot merged commit a11224a into master Jul 1, 2024
57 of 58 checks passed
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.0-alpha.3-proton branch July 1, 2024 22:38
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