Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork408
[skip changelog] Bump github.com/ProtonMail/go-crypto from 1.2.0 to 1.3.0#2918
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
dependabot wants to merge1 commit intomasterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Open
[skip changelog] Bump github.com/ProtonMail/go-crypto from 1.2.0 to 1.3.0#2918
dependabot wants to merge1 commit intomasterfromdependabot/go_modules/github.com/ProtonMail/go-crypto-1.3.0
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.2.0 to 1.3.0.- [Release notes](https://github.com/ProtonMail/go-crypto/releases)- [Commits](ProtonMail/go-crypto@v1.2.0...v1.3.0)---updated-dependencies:- dependency-name: github.com/ProtonMail/go-crypto dependency-version: 1.3.0 dependency-type: direct:production update-type: version-update:semver-minor...Signed-off-by: dependabot[bot] <support@github.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumpsgithub.com/ProtonMail/go-crypto from 1.2.0 to 1.3.0.
Release notes
Sourced fromgithub.com/ProtonMail/go-crypto's releases.
Commits
3b22d85Merge pull request#286 from ProtonMail/feat/v1-api-enforce-signature-hashesa9af95cfeat(v1): Only allow acceptable hashes when writing signatures3c60603Merge pull request#285 from ProtonMail/feat/decompression-size-limitd664700feat: Allow to set a decompressed size limite1ea40eMerge pull request#281 from ProtonMail/fix/clearsign-check-hash9cd4c3afeat(clearsign): Write complete legacy hash header244eb1cfix(clearsign): Enforce acceptable hash functions in clearsigna994e32Merge pull request#284 from ProtonMail/feat/less-restrictive-key-signature8fe0e95feat(v2): Tolerate invalid key signatures if one passesYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)