Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Nov 3, 2025

Update Request | Renovate Bot

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
github.com/ProtonMail/gopenpgp/v2 v2.9.0 -> v3.3.0 age adoption passing confidence require major
github.com/cenkalti/backoff/v4 v4.3.0 -> v5.0.3 age adoption passing confidence require major
github.com/planetscale/vtprotobuf 0393e58 -> ba97887 require digest
github.com/siderolabs/gen v0.8.5 -> v0.8.6 age adoption passing confidence require patch
go.yaml.in/yaml/v4 v4.0.0-rc.2 -> v4.0.0-rc.3 age adoption passing confidence require patch
golang.org/x/sync v0.17.0 -> v0.18.0 age adoption passing confidence require minor

Release Notes

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

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.

cenkalti/backoff (github.com/cenkalti/backoff/v4)

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

siderolabs/gen (github.com/siderolabs/gen)

v0.8.6

Compare Source

gen 0.8.6 (2025-11-03)

Welcome to the v0.8.6 release of gen!

Please try out the release binaries and report any issues at
https://github.com/siderolabs/gen/issues.

Contributors
  • Dmitriy Matrenichev
  • Artem Chernyshev
  • Utku Ozdemir
  • Andrey Smirnov
  • Andrey Smirnov
  • Dmitriy Matrenichev
  • Mateusz Urbanek
Changes
27 commits

  • 4c7388b chore: update Go modules, replace YAML library
  • 044d921 feat: add xslices.Deduplicate
  • dcb2b74 feat: add panicsafe package
  • b36ee43 feat: make xyaml.CheckUnknownKeys public
  • 3e319e7 feat: implement xyaml.UnmarshalStrict
  • 7c0324f chore: future-proof HashTrieMap
  • 5ae3afe chore: update hashtriemap implementation from the latest upstream
  • e847d2a chore: add more utilities to xiter
  • f3c5a2b chore: add Empty and Empty2 iterators
  • c53b90b chore: add packages xiter/xstrings/xbytes
  • 7654108 chore: add hashtriemap implementation
  • 8485864 chore: optimize maps.Values and maps.Keys
  • 238baf9 chore: add typesafe SyncMap and bump stuff
  • efca710 chore: add FilterInPlace method to maps and update module
  • 36a3ae3 feat: update module
  • f9f5805 chore: bump rekres and add functions from exp
  • b968d21 feat: add TryRecv and RecvWithContext functions
  • 476dfea feat: add foreach and clear to lazymap
  • 214c1ef chore: set slice.Filter result slice cap to len
  • 8e89b1e feat: add GetOrCreate and GetOrCall methods
  • 7c7ccc3 feat: introduce channel SendWithContext
  • b3b6db8 fix: fix Copy documentation and implementation
  • 521f737 feat: add xerrors package which contains additions to the std errors
  • 726e066 fix: rename tuples.go to pair.go and set proper package name
  • d8d7d25 chore: minor additions
  • 338a650 chore: add initial implementation and documentation
  • 4fd8667 Initial commit

Changes since v0.8.5
1 commit

  • 4c7388b chore: update Go modules, replace YAML library

Dependency Changes

This release has no dependency changes

yaml/go-yaml (go.yaml.in/yaml/v4)

v4.0.0-rc.3

Compare Source


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@github-project-automation github-project-automation bot moved this to To Do in Planning Nov 3, 2025
@talos-bot talos-bot moved this from To Do to In Review in Planning Nov 3, 2025
@smira smira removed this from Planning Nov 3, 2025
@renovate renovate bot force-pushed the renovate/dependencies branch 2 times, most recently from 013d3a3 to 02df47f Compare November 3, 2025 14:59
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/dependencies branch from 02df47f to 13c03d4 Compare November 9, 2025 07:58
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