Skip to content

fix(deps): update module github.com/protonmail/gopenpgp/v2 to v3 - #3039

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-protonmail-gopenpgp-v2-3.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-protonmail-gopenpgp-v2-3.x

Conversation

@renovate

@renovate renovate Bot commented Sep 5, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/ProtonMail/gopenpgp/v2 v2.10.0 → v3.5.1 age confidence

Release Notes

ProtonMail/gopenpgp (github.com/ProtonMail/gopenpgp/v2)

v3.5.1

Compare Source

What's Changed

Full Changelog: ProtonMail/gopenpgp@v3.5.0...v3.5.1

v3.5.0

Compare Source

What's Changed
  • Improve robustness agains invalid input in #​365
  • Bump to latest go-crypto fork version v1.5.2 in #​368

Full Changelog: ProtonMail/gopenpgp@v3.4.1...v3.5.0

v3.4.1

Compare Source

What's Changed

  • Fix EOF behavior of the verification Reader in #​358

Full Changelog: ProtonMail/gopenpgp@v3.4.0...v3.4.1

v3.4.0

Compare Source

What's Changed

Added
  • InsecureAllowAllKeyFlagsWhenMissing profile option. Allows usage of keys without key flags.
Changed
  • Update go-crypto fork to v1.4.1.

Full Changelog: ProtonMail/gopenpgp@v3.3.0...v3.4.0

v3.3.0

Compare Source

What's Changed
Added
  • MaxDecompressedSize option to control the maximum size of decompressed messages.
Changed
  • Update go-crypto to v1.3.0.

Full Changelog: ProtonMail/gopenpgp@v3.2.1...v3.3.0

v3.2.1

Compare Source

What's Changed

Fixed
  • Avoid double compression in signcryption with a session key by @​lubux in #​337

Full Changelog: ProtonMail/gopenpgp@v3.2.0...v3.2.1

v3.2.0

Compare Source

What's Changed
Added
Changed
  • Bumped minimum supported Go version to 1.22.0.
  • Update go-crypto fork to v1.2.0.
  • Remove pkgs/errors dependency.

Full Changelog: ProtonMail/gopenpgp@v3.1.3...v3.2.0

v3.1.3

Compare Source

What's Changed
Changed
  • Update go-crypto fork to v1.1.6

Full Changelog: ProtonMail/gopenpgp@v3.1.2...v3.1.3

v3.1.2

Compare Source

What's Changed
Changed
  • Update go-crypto fork to v1.1.5

Full Changelog: ProtonMail/gopenpgp@v3.1.1...v3.1.2

v3.1.1

Compare Source

What's Changed
Changed
  • Update go-crypto fork to v1.1.4

Full Changelog: ProtonMail/gopenpgp@v3.1.0...v3.1.1

v3.1.0

Compare Source

What's Changed
Added
Changed
  • Adapt to go-crypto cleartext API changes by @​lubux in #​310
  • Rename profile.Custom.AllowWeakRSA to profile.Custom.InsecureAllowWeakRSA
  • Update go-crypto fork to v1.1.3

Full Changelog: ProtonMail/gopenpgp@v3.0.0...v3.1.0

v3.0.0

Compare Source

What's Changed
New simplified and unified API

GopenPGP v3 introduces a new unified API for high level OpenPGP operations. In comparison to GopenPGP v2, where similar functions were dispersed across different types and required varying implementations for the same operations, GopenPGP v3 consolidates these functions into a consistent interface. Now, operations such as Sign, Verify, Encrypt, Decrypt, and Key generation are each accessible through a unified, builder like API, simplifying integration and enhancing code readability across cryptographic workflows.

However, applications migrating from v2 to v3 will need to update their API calls, as the changes are not backward-compatible. This means that all previous API calls must be rewritten to align with the new, unified API structure. GopenPGP v3 supports the migration process by offering extensive documentation and practical examples. We recommend upgrading to v3 for the latest features and improvements, but we'll continue to support GopenPGP v2 for the time being. Our support includes ongoing bug fixes and minor feature updates to ensure stability and functionality for existing users.

For usage examples of the new API, see the README. For the full documentation, see https://pkg.go.dev/github.com/ProtonMail/gopenpgp/v3.

Profiles

GopenPGP v3 introduces the concept of profiles, enabling applications to configure OpenPGP algorithm selection based on their specific needs. For most applications, the provided preset profiles offer robust and secure defaults, eliminating the need for additional configuration.

RFC 9580 and Interoperability

GopenPGP v3 adds full support for the latest OpenPGP specification, RFC 9580. Compliance with the specification has also been significantly enhanced, as confirmed by the results in the OpenPGP interoperability test suite. These enhancements in GopenPGP v3 are possible by leveraging a new API in the go-crypto fork, which enables a range of improvements in functionality, compliance, and performance.

Go Mobile Support

GopenPGP v3 aims to be fully compatible with Gomobile to provide an API for mobile platforms. For this reason, the library defaults to a builder-like pattern, which is less commonly used in Go. All code that is only relevant for mobile platforms has been moved to the mobile module.

Extending Functionality

GopenPGP v3 introduces a streaming interface across all APIs, enabling memory efficient processing of large data.
Additionally, it extends the library's functionality with various improvements, such as:

  • Consider all signatures in a message during verification and allow inspection of each.
  • Support signing with multiple keys.
  • Support encrypting to an "anonymous recipient", where the recipient KeyID is represented as all zeros in the message.
  • Add support for the intended recipient feature as specified in RFC 9580.
  • Ensure consistent behaviour across all APIs.
  • Support generating v6 keys as specified in RFC 9580.

Full Changelog: ProtonMail/gopenpgp@v2.7.5...v3.0.0.

Changelog since v3.0.0-beta.0: ProtonMail/gopenpgp@v3.0.0-beta.0...v3.0.0.

v2.11.0

Compare Source

What's Changed

Full Changelog: ProtonMail/gopenpgp@v2.10.0...v2.11.0


Configuration

📅 Schedule: (UTC)

  • 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/github.com-protonmail-gopenpgp-v2-3.x branch from a02c07c to 25d7804 Compare September 7, 2026 17:07
@renovate
renovate Bot force-pushed the renovate/github.com-protonmail-gopenpgp-v2-3.x branch 2 times, most recently from e08fe68 to 0263b81 Compare September 16, 2026 10:07

@pikachuren pikachuren left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏 感谢 @app/renovate 提交!
🤖 AI 自动审核声明:本评审报告由 AI 自动生成,当前使用 Claude Opus 5 模型进行分析。
⚠️ AI 分析结果仅供参考,可能存在误判或遗漏。如您发现任何问题或有不同意见,欢迎随时提出讨论和纠正。
⚠️ 重要提醒:即使 AI 评审认为代码质量良好且建议合并,最终是否合并仍需由项目维护者进行人工判定。项目维护者会综合考虑代码质量、项目规划、技术方向、团队资源等多方面因素做出是否合并的决策。

🎯 结论

✅ Approve — 代码质量良好,建议合并

📖 概要

fix(deps): update module github.com/protonmail/gopenpgp/v2 to v3

📊 评审结果

改动合理,无重大问题发现。代码逻辑清晰,符合项目规范。

🎯 结论:✅ Approve — 建议合并

@renovate
renovate Bot force-pushed the renovate/github.com-protonmail-gopenpgp-v2-3.x branch 3 times, most recently from 76ab122 to bf5a3ab Compare September 28, 2026 22:08
@renovate

renovate Bot commented Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
github.com/ProtonMail/go-crypto v1.4.1 -> v1.5.2

@renovate
renovate Bot force-pushed the renovate/github.com-protonmail-gopenpgp-v2-3.x branch from bf5a3ab to c1c4b13 Compare September 29, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant