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.1.2
v2.7.5
->v2.8.0
v0.5.0
->v0.5.3
v2.22.0
->v2.23.0
v1.66.0
->v1.68.0
v1.34.2
->v1.35.2
Release Notes
ProtonMail/go-crypto (github.com/ProtonMail/go-crypto)
v1.1.2
Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.1...v1.1.2
v1.1.1
Compare Source
What's Changed
clearsign.Encode
backwards compatibility #239 by @mdosch in https://github.com/ProtonMail/go-crypto/pull/240Full Changelog: ProtonMail/go-crypto@v1.1.0...v1.1.1
v1.1.0
Compare 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
openpgp
package remains fully backwards compatible while the new v2 API is located in a separatev2
package 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-proton
Compare 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-proton
Compare 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.0
Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.5...v1.1.0-beta.0
v1.1.0-alpha.5-proton
Compare 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-proton
Compare 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-proton
Compare 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-proton
Compare Source
v1.1.0-alpha.1-proton
Compare 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)
v2.8.0
Compare 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.3
Compare Source
Changelog
xdg.SearchRuntimeFile
to 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.RuntimeFile
suggests the operating system's temporary directory as a suitable fallback location.Internal
v0.5.2
Compare 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 directory
as 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.1
Compare Source
Changelog
XDG_BIN_HOME
base directory.See XDG base directories README section for more details.
macOS
.~/.config
at the end of the list of default locations forXDG_CONFIG_DIRS
.~/.local/share
at the end of the list of default locations forXDG_DATA_DIRS
.Windows
:%ProgramFiles%
%ProgramFiles%\Common Files
%LOCALAPPDATA%\Programs
%LOCALAPPDATA%\Programs\Common
Internal
golang.org/x/sys
dependency to the latest version.grpc-ecosystem/grpc-gateway (github.com/grpc-ecosystem/grpc-gateway/v2)
v2.23.0
Compare Source
What's Changed
New Contributors
Full Changelog: grpc-ecosystem/grpc-gateway@v2.22.0...v2.23.0
grpc/grpc-go (google.golang.org/grpc)
v1.68.0
: Release 1.68.0Compare Source
Behavior Changes
ClientConn.Close()
now closes transports simultaneously and waits for transports to be closed before returning. (#7666)NewTLS
that usetls.Config.GetConfigForClient
will now have CipherSuites, supported TLS versions and ALPN configured automatically. These were previously only set for configs not using theGetConfigForClient
option. (#7709)Bug Fixes
Dependencies
go1.22.7
. (#7624)v1.67.1
: Release 1.67.1Compare Source
Bug Fixes
v1.67.0
: Release 1.67.0Compare Source
Bug Fixes
Behavior Changes
GRPC_ENFORCE_ALPN_ENABLED
tofalse
(case insensitive). Please file a bug if you encounter any issues with this behavior. The environment variable to revert this behavior will be removed in an upcoming release. (#7535)v1.66.3
: Release 1.66.3Compare Source
Bug Fixes
v1.66.2
: Release 1.66.2Compare Source
Dependencies
testing
package (#7579)flate
package (#7595)Bug Fixes
v1.66.1
Compare Source
protocolbuffers/protobuf-go (google.golang.org/protobuf)
v1.35.2
Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.35.1...v1.35.2
Maintenance:
CL/623115: proto: refactor equal_test from explicit table to use makeMessages()
CL/623116: encoding/prototext: use testmessages_test.go approach, too
CL/623117: internal/testprotos/test: add nested message field with [lazy=true]
CL/624415: proto: switch messageset_test to use makeMessages() injection point
CL/624416: internal/impl: fix TestMarshalMessageSetLazyRace (was a no-op!)
User-visible changes:
CL/618395: encoding/protojson: allow missing value for Any of type Empty
CL/618979: all: implement strip_enum_prefix editions feature
CL/622575: testing/protocmp: document behavior when combining Ignore and Sort
v1.35.1
Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.34.2...v1.35.1
Maintenance:
User-visible changes:
Bug fixes:
v1.35.0
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (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.