Update module github.com/go-logr/logr to v1.4.3#179
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
96c9098 to
f28904d
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
f28904d to
b754d3d
Compare
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
b754d3d to
6ce38bd
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
6ce38bd to
246b359
Compare
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
246b359 to
380229f
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
380229f to
17dd699
Compare
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
17dd699 to
b995e5b
Compare
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
b995e5b to
c944d53
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.2.4→v1.4.3Release Notes
go-logr/logr (github.com/go-logr/logr)
v1.4.3Compare Source
Minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.4.2...v1.4.3
v1.4.2Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan 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
v1.3.0Compare Source
This release adds support for slog in a new, self-contained
logr/slogrpackage. Implementers of alogr.LogSinkare encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslogAPI call.Breaking change: the call depth for
LogSink.Enabledwhen called viaLogger.Enabledwas fixed to be the same as for other call paths. Implementers of aLogSinkwho have worked around this bug will need to remove their workarounds.Security best practices were improved. Only Go versions >= 1.18 are supported by this release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.4...v1.3.0
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.