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

Bump github.com/ProtonMail/go-crypto from 1.1.0-alpha.2 to 1.1.0-alpha.2-proton #757

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 19, 2024

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

Release notes

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

v1.1.0-alpha.1-proton

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

v1.1.0-alpha.0-proton

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

Commits
  • 91b9355 Fix HMAC generation (#204)
  • 65ad1e4 Replace ioutil.ReadAll with io.ReadAll
  • 54e58ae fix(v2): Adapt NewForwardingEntity to refactored NewEntity
  • 16f8541 fix(v2): Do not allow encrpytion with a forwarding key
  • 28d1c85 feat: Add symmetric keys to v2
  • c99f7e5 fix: Address warnings
  • d5a01d4 feat: Add forwarding to v2 api
  • 5b0fb2f fix: Address rebase on version 2 issues
  • b188297 Use fingerprints instead of KeyIDs
  • 26779fb 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)

@dependabot dependabot bot requested a review from a team as a code owner June 19, 2024 23:12
@dependabot dependabot bot added the failure:update-dependencies An issue filed automatically when updating buildpack.toml dependencies fails in a workflow label Jun 19, 2024
@paketo-bot paketo-bot added the semver:patch A change requiring a patch version bump label Jun 19, 2024
@paketo-bot paketo-bot enabled auto-merge (rebase) June 19, 2024 23:18
Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.1.0-alpha.2 to 1.1.0-alpha.2-proton.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.0-alpha.2...v1.1.0-alpha.2-proton)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.0-alpha.2-proton branch from 15429ba to 83746a5 Compare June 19, 2024 23:19
@paketo-bot paketo-bot merged commit df5804d into main Jun 19, 2024
10 checks passed
@paketo-bot paketo-bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.0-alpha.2-proton branch June 19, 2024 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failure:update-dependencies An issue filed automatically when updating buildpack.toml dependencies fails in a workflow semver:patch A change requiring a patch version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants