chore: update dependencies #45
Open
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.
Update Request | Renovate Bot
This PR contains the following updates:
v1.1.0-alpha.5.0.20240827111422-b5837fa4476e->v1.3.0v2.7.5->v3.3.0v0.5.0->v0.5.3v2.22.0->v2.27.30393e58->ba97887v1.9.0->v1.11.1v0.24.0->v0.38.0v1.66.0->v1.77.0v1.34.2->v1.36.10Release Notes
ProtonMail/go-crypto (github.com/ProtonMail/go-crypto)
v1.3.0Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.2.0...v1.3.0
v1.2.0Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.6...v1.2.0
v1.1.6Compare Source
What's Changed
PublicKey.KeyIdStringto return a valid key id by @lubux in #269Full Changelog: ProtonMail/go-crypto@v1.1.5...v1.1.6
v1.1.5Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.4...v1.1.5
v1.1.4Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.3...v1.1.4
v1.1.3Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.2...v1.1.3
v1.1.2Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.1...v1.1.2
v1.1.1Compare Source
What's Changed
clearsign.Encodebackwards compatibility #239 by @mdosch in #240Full Changelog: ProtonMail/go-crypto@v1.1.0...v1.1.1
v1.1.0Compare Source
What's Changed
This release adds full support for the new version of the OpenPGP standard, RFC 9580. In addition, the release introduces an improved non-backwards compatible v2 API. The API in the
openpgppackage remains fully backwards compatible while the new v2 API is located in a separatev2package inopenpgp.For the full changes since
v1.0.0, see the previous release notes. For the full changelog, see ProtonMail/go-crypto@v1.0.0...v1.1.0.Changes since
v1.1.0-beta.0:Changelog since
v1.1.0-beta.0: ProtonMail/go-crypto@v1.1.0-beta.0...v1.1.0.v1.1.0-protonCompare Source
What's Changed
This release is v1.1.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-beta.0-protonCompare Source
This pre-release is v1.1.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-beta.0Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.5...v1.1.0-beta.0
v1.1.0-alpha.5-protonCompare Source
This pre-release is v1.1.0-alpha.5 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-alpha.4-protonCompare Source
This pre-release is v1.1.0-alpha.4 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-alpha.3-protonCompare Source
This pre-release is v1.1.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
v1.1.0-alpha.2-protonCompare Source
v1.1.0-alpha.1-protonCompare Source
This pre-release is v1.1.0-alpha.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.
ProtonMail/gopenpgp (github.com/ProtonMail/gopenpgp/v2)
v3.3.0Compare Source
What's Changed
Added
Changed
Full Changelog: ProtonMail/gopenpgp@v3.2.1...v3.3.0
v3.2.1Compare Source
What's Changed
Fixed
Full Changelog: ProtonMail/gopenpgp@v3.2.0...v3.2.1
v3.2.0Compare Source
What's Changed
Added
Changed
1.22.0.v1.2.0.pkgs/errorsdependency.Full Changelog: ProtonMail/gopenpgp@v3.1.3...v3.2.0
v3.1.3Compare Source
What's Changed
Changed
v1.1.6Full Changelog: ProtonMail/gopenpgp@v3.1.2...v3.1.3
v3.1.2Compare Source
What's Changed
Changed
v1.1.5Full Changelog: ProtonMail/gopenpgp@v3.1.1...v3.1.2
v3.1.1Compare Source
What's Changed
Changed
v1.1.4Full Changelog: ProtonMail/gopenpgp@v3.1.0...v3.1.1
v3.1.0Compare Source
What's Changed
Added
Changed
profile.Custom.AllowWeakRSAtoprofile.Custom.InsecureAllowWeakRSAv1.1.3Full Changelog: ProtonMail/gopenpgp@v3.0.0...v3.1.0
v3.0.0Compare 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
mobilemodule.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:
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.9.0Compare Source
What's Changed
Changed
v1.3.0.1.22.0.Full Changelog: ProtonMail/gopenpgp@v2.8.3...v2.9.0
v2.8.3Compare Source
What's Changed
Changed
v1.1.6Full Changelog: ProtonMail/gopenpgp@v2.8.2...v2.8.3
v2.8.2Compare Source
What's Changed
Changed
v1.1.4Full Changelog: ProtonMail/gopenpgp@v2.8.1...v2.8.2
v2.8.1Compare Source
What's Changed
Changed
v1.1.3Full Changelog: ProtonMail/gopenpgp@v2.8.0...v2.8.1
v2.8.0Compare Source
What's Changed
Support for RFC 9580
Adds support for reading and writing messages with RFC 9580 by updating the underlying go-crypto fork library to the latest version. Note that GopenPGP v2 currently does not support:
For full RFC 9580 support, we recommend upgrading to GopenPGP v3.
Full Changelog: ProtonMail/gopenpgp@v2.7.5...v2.8.0
adrg/xdg (github.com/adrg/xdg)
v0.5.3Compare Source
Changelog
xdg.SearchRuntimeFileto also look in the operating system's temporary directory for runtime files.This covers unlikely cases in which runtime files cannot be written relative to the base runtime directory either because it does not exist or it is not accessible, so
xdg.RuntimeFilesuggests the operating system's temporary directory as a suitable fallback location.Internal
v0.5.2Compare Source
Changelog
Updated logic of
xdg.RuntimeFile: due to the special nature of theruntime directory, the function no longer attempts to create it if it does not exist. If that's the case, the function uses the operating system'stemporary directoryas a fallback. The function still creates subdirectories relative to the base runtime directory or its fallback.Justification: the creation of the runtime directory is not in the scope of this package as it has special requirements defined by the XDG Base Directory Specification. Relevant excerpt:
Also, on
Linux, the parent directories of the default user runtime directory are owned by the root user so they cannot be created by a regular user. pam_systemd is usually responsible for creating the runtime directory (/run/user/$UID).v0.5.1Compare Source
Changelog
XDG_BIN_HOMEbase directory.See XDG base directories README section for more details.
macOS.~/.configat the end of the list of default locations forXDG_CONFIG_DIRS.~/.local/shareat the end of the list of default locations forXDG_DATA_DIRS.Windows:%ProgramFiles%%ProgramFiles%\Common Files%LOCALAPPDATA%\Programs%LOCALAPPDATA%\Programs\CommonInternal
golang.org/x/sysdependency to the latest version.grpc-ecosystem/grpc-gateway (github.com/grpc-ecosystem/grpc-gateway/v2)
v2.27.3Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.27.2...v2.27.3
v2.27.2Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.27.1...v2.27.2
v2.27.1Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.27.0...v2.27.1
v2.27.0Compare Source
What's Changed
camelCaseby @iamrajiv in #5601New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.26.3...v2.26.4
v2.26.3Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.26.2...v2.26.3
v2.26.2Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.26.1...v2.26.2
v2.26.1Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.26.0...v2.26.1
v2.26.0Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.25.1...v2.26.0
v2.25.1Compare Source
Support the new Opaque API in openapiv2 generated files
This release contains breaking changes from v2.25.0, in that the previously deprecated
EnumDescriptorandDescriptormethods on the struct types in the openapiv2 options package have been removed. This seems to be a requirement to generate the new Hybrid API. Please open an issue if you were depending on these functions and we'll see what we can do about it.What's Changed
Full Changelog: grpc-ecosystem/grpc-gateway@v2.25.0...v2.25.1
v2.25.0Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.24.0...v2.25.0
v2.24.0Compare Source
What's Changed
customizing_your_gateway.mdreference by @emmanuel-ferdman in #4940buildtoolsdependency by @AlejoAsd in #4980New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.23.0...v2.24.0
v2.23.0Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.22.0...v2.23.0
stretchr/testify (github.com/stretchr/testify)
v1.11.1Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
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 is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.