8000 Bump github.com/ProtonMail/go-crypto from 1.1.6 to 1.2.0 by dependabot[bot] · Pull Request #377 · DataDog/nikos · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bump github.com/ProtonMail/go-crypto from 1.1.6 to 1.2.0 #377

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

Conversation

dependabot[bot]
Copy link
Contributor
@dependabot dependabot bot commented on behalf of github Apr 14, 2025

Bumps github.com/ProtonMail/go-crypto from 1.1.6 to 1.2.0.

Release notes

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

v1.2.0

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.6...v1.2.0

Release v1.2.0-proton

What's Changed

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

Commits
  • 70930d7 Merge pull request #280 from ProtonMail/fix/aead-max-chunk-size
  • 54e82fd fix: The max AEAD chunk size must be 4MiB not 65KiB
  • 61ae167 Merge pull request #278 from ProtonMail/chore/bump-go-version
  • af200f2 chore: Update min go version to 1.22.0
  • 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.6 to 1.2.0.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.6...v1.2.0)

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

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 Apr 14, 2025
@dependabot dependabot bot requested a review from a team as a code owner April 14, 2025 05:10
Copy link
Contributor Author
dependabot bot commented on behalf of github May 26, 2025

Superseded by #380.

@dependabot dependabot bot closed this May 26, 2025
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.2.0 branch May 26, 2025 05:43
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
0