🌱 Update Update Golang Dependencies group (minor) #1090
Merged
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.
This PR contains the following updates:
v1.3.0
->v1.4.1
v2.4.0
->v2.5.1
Release Notes
go-logr/logr (github.com/go-logr/logr)
v1.4.1
Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0
Compare Source
This release dramatically improves interoperability with Go's
log/slog
package. In particular,logr.NewContext
andlogr.NewContextWithSlogLogger
use the same context key, which allowslogr.FromContext
andlogr.FromContextAsSlogLogger
to returnlogr.Logger
or*slog.Logger
respectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLogr
andlogr/slogr.ToSlogHandler
have been superceded bylogr.FromSlogHandler
andlogr.ToSlogHandler
respectively, and typelogr/slogr.SlogSink
has been superceded bylogr.SlogSink
. All of the old names inlogr/slogr
remain, for compatibility.Package
logr/funcr
now supportslogr.SlogSink
, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncr
handles the timestamp itself).Users who have a
logr.Logger
and need a*slog.Logger
can callslog.New(logr.ToSlogHandler(...))
and all output will go through the same stack.Users who have a
*slog.Logger
orslog.Handler
can calllogr.FromSlogHandler(...)
and all output will go through the same stack.What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.3.0...v1.4.0
hetznercloud/hcloud-go (github.com/hetznercloud/hcloud-go/v2)
v2.5.1
Compare Source
Bug Fixes
v2.5.0
Compare Source
Features
Bug Fixes
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 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.