← Back to issue list

fix(deps): update module github.com/protonmail/go-crypto to v1.1.3

View original Github issue

Metadata

Project
fetch-service
Number
#286
Type
pull request
State
closed
Author
renovate[bot]
Labels
—
Created
Updated
Closed

Current evaluation

Renovate PR to bump github.com/ProtonMail/go-crypto v1.0.0 -> v1.1.3 was approved but closed unmerged; Renovate ignored v1.1.3 and a later PR landed v1.1.5 instead.

Resolution: closed superseded

Reason: The PR was closed without merging — the bot's closing comment (2024-12-12) confirms Renovate will ignore v1.1.3 until a newer version is released. The go.mod history shows the dependency jumped from v1.0.0 to v1.1.5 via commit 53e26a0 (PR #348), so the target version was never applied and was overtaken by a later release.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/ProtonMail/go-crypto](https://redirect.github.com/ProtonMail/go-crypto) | `v1.0.0` -> `v1.1.3` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fProtonMail%2fgo-crypto/v1.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fProtonMail%2fgo-crypto/v1.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fProtonMail%2fgo-crypto/v1.0.0/v1.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fProtonMail%2fgo-crypto/v1.0.0/v1.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>ProtonMail/go-crypto (github.com/ProtonMail/go-crypto)</summary> ### [`v1.1.3`](https://redirect.github.com/ProtonMail/go-crypto/releases/tag/v1.1.3) [Compare Source](https://redirect.github.com/ProtonMail/go-crypto/compare/v1.1.2...v1.1.3) #### What's Changed - Add argon2 test vector for 32-bit platforms by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/245](https://redirect.github.com/ProtonMail/go-crypto/pull/245) - Validate argon2 params on read by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/246](https://redirect.github.com/ProtonMail/go-crypto/pull/246) - Adapt aead preferences on key generation by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/248](https://redirect.github.com/ProtonMail/go-crypto/pull/248) - Improve AEAD handling by [@&#8203;twiss](https://redirect.github.com/twiss) in [https://github.com/ProtonMail/go-crypto/pull/247](https://redirect.github.com/ProtonMail/go-crypto/pull/247) - Improve error message for decryption with a session key by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/237](https://redirect.github.com/ProtonMail/go-crypto/pull/237) - Flag to allow signing key decryption by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/251](https://redirect.github.com/ProtonMail/go-crypto/pull/251) **Full Changelog**: https://github.com/ProtonMail/go-crypto/compare/v1.1.2...v1.1.3 ### [`v1.1.2`](https://redirect.github.com/ProtonMail/go-crypto/releases/tag/v1.1.2) [Compare Source](https://redirect.github.com/ProtonMail/go-crypto/compare/v1.1.1...v1.1.2) #### What's Changed - Cleartext Framework: Exclude the line-ending separator when decoding plaintext by [@&#8203;lubux](https://redirect.github.com/lubux) in [https://github.com/ProtonMail/go-crypto/pull/242](https://redirect.github.com/ProtonMail/go-crypto/pull/242) **Full Changelog**: https://github.com/ProtonMail/go-crypto/compare/v1.1.1...v1.1.2 ### [`v1.1.1`](https://redirect.github.com/ProtonMail/go-crypto/releases/tag/v1.1.1) [Compare Source](https://redirect.github.com/ProtonMail/go-crypto/compare/v1.1.0...v1.1.1) #### What's Changed - Fix `clearsign.Encode` backwards compatibility [#&#8203;239](https://redirect.github.com/ProtonMail/go-crypto/issues/239) by [@&#8203;mdosch](https://redirect.github.com/mdosch) in [https://github.com/ProtonMail/go-crypto/pull/240](https://redirect.github.com/ProtonMail/go-crypto/pull/240) **Full Changelog**: https://github.com/ProtonMail/go-crypto/compare/v1.1.0...v1.1.1 ### [`v1.1.0`](https://redirect.github.com/ProtonMail/go-crypto/releases/tag/v1.1.0) [Compare Source](https://redirect.github.com/ProtonMail/go-crypto/compare/v1.0.0...v1.1.0) #### What's Changed This release adds full support for the new version of the OpenPGP standard, [RFC 9580](https://www.rfc-editor.org/rfc/rfc9580.html). In addition, the release introduces an improved non-backwards compatible v2 API. The API in the `openpgp` package remains fully backwards compatible while the new v2 API is located in a separate `v2` package in `openpgp`. For the full changes since `v1.0.0`, see the previous release notes. For the full changelog, see https://github.com/ProtonMail/go-crypto/compare/v1.0.0...v1.1.0. Changes since `v1.1.0-beta.0`: - Replace expiring curve448 integration test vector by [@&#8203;lubux](https://redirect.github.com/lubux) - Validate input key size in SEIPDv2 decryption by [@&#8203;lubux](https://redirect.github.com/lubux) **Changelog since `v1.1.0-beta.0`**: https://github.com/ProtonMail/go-crypto/compare/v1.1.0-beta.0...v1.1.0. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/fetch-service). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS43LjEiLCJ1cGRhdGVkSW5WZXIiOiIzOS4xOS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed superseded Renovate PR to bump github.com/ProtonMail/go-crypto v1.0.0 -> v1.1.3 was approved but closed unmerged; Renovate ignored v1.1.3 and a later PR landed v1.1.5 instead.
stealth/space-bunny-alpha — closed stale PR #286 was closed unmerged after approval. Renovate ignored the v1.1.3 update pending a newer release; v1.1.5 later landed via #348 (53e26a0).
qwen/qwen3.6-35b-a3b — — The dependency update to github.com/protonmail/go-crypto v1.1.3 was abandoned and closed without merging. Renovate confirmed the action and will ignore this update, waiting for a newer version instead.

Update history

Date Change
created

Related work

  • Superseded By: canonical/fetch-service#348 (confidence 95%)

    Commit 53e26a0 'build(deps): update go-crypto to v1.1.5 (#348)' is the first go-crypto bump after v1.0.0 in go.mod history, replacing the skipped v1.1.3 update.

  • Related To: canonical/fetch-service#350 (confidence 70%)

    Subsequent Renovate bump to v1.1.6 (commit de96aa0), continuing the upgrade chain that superseded this PR.

Related issues

Issue Project State Summary Similarity
#350 fix(deps): update module github.com/protonmail/go-crypto to v1.1.6 fetch-service merged Renovate PR #350 bumped github.com/ProtonMail/go-crypto v1.1.5 -> v1.1.6 and was merged into main via commit de96aa0, updating go.mod and go.sum.
95%
#390 fix(deps): update module github.com/protonmail/go-crypto to v1.3.0 fetch-service merged Renovate PR #390 merged, bumping github.com/ProtonMail/go-crypto v1.2.0 to v1.3.0 in commit 5c2348c. Later superseded by go-crypto v1.4.0/v1.4.1/v1.5.1/v1.5.2.
95%
#322 fix(deps): update module github.com/protonmail/go-crypto to v1.1.5 fetch-service closed Renovate PR bumping ProtonMail/go-crypto v1.0.0 -> v1.1.5 was closed unmerged by maintainer cmatsuoka on 2025-02-23 as "Superseded by #348", which landed the same bump in commit 53e26a0.
95%
#379 fix(deps): update module github.com/protonmail/go-crypto to v1.2.0 fetch-service merged Renovate dependency bump of github.com/ProtonMail/go-crypto v1.1.6 -> v1.2.0 (plus transitive circl v1.3.7 -> v1.6.0) was approved by two reviewers and merged into main in commit 7ad8f54, changing go.mod/go.sum.
92%
#584 fix(deps): update module github.com/protonmail/go-crypto to v1.4.1 fetch-service merged Renovate PR merged, bumping github.com/ProtonMail/go-crypto from v1.4.0 to v1.4.1 (go.mod/go.sum) in commit 68bf1a2. Later superseded by v1.5.1 (#650) and v1.5.2 (#658).
92%
#578 fix(deps): update module github.com/protonmail/go-crypto to v1.4.0 fetch-service merged Renovate PR merged as commit bf599c8, bumping github.com/ProtonMail/go-crypto v1.3.0 → v1.4.0 (also pulling cloudflare/circl v1.6.1 → v1.6.2). Later superseded by #584 (v1.4.1), #650 (v1.5.1) and #658 (v1.5.2).
91%
#650 fix(deps): update module github.com/protonmail/go-crypto to v1.5.1 fetch-service merged Renovate PR #650 merged into main, bumping github.com/ProtonMail/go-crypto v1.4.1 -> v1.5.1 in go.mod/go.sum (+3/-1), picking up upstream hardening for malformed OpenPGP input. Superseded later by #658 (v1.5.2).
91%
#658 fix(deps): update module github.com/protonmail/go-crypto to v1.5.2 fetch-service merged Renovate PR #658 bumped github.com/ProtonMail/go-crypto from v1.5.1 to v1.5.2 (RSA key prime-ordering serialization fix) and was merged into main, updating go.mod/go.sum (+3/-1).
90%
#348 build(deps): update go-crypto to v1.1.5 fetch-service merged Merged PR #348 (commit 53e26a0) bumped github.com/ProtonMail/go-crypto to v1.1.5; shipped in fetch-service 0.7.0 (2025-04-08) as "fix(deps): update go-crypto to v1.1.5".
82%
#643 fix(deps): update module golang.org/x/crypto to v0.57.0 fetch-service closed Renovate PR #643 was closed unmerged; x/crypto v0.57.0 never reached main, which remains on v0.55.0.
75%