Update module github.com/go-logr/logr to v1 #45
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:
v0.4.0
->v1.4.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
v1.3.0
Compare Source
This release adds support for slog in a new, self-contained
logr/slogr
package. Implementers of alogr.LogSink
are encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslog
API call.Breaking change: the call depth for
LogSink.Enabled
when called viaLogger.Enabled
was fixed to be the same as for other call paths. Implementers of aLogSink
who 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
v1.2.4
Compare Source
This is a collection of small bugfixes and documentation updates.
NOTE: A change (https://github.com/go-logr/logr/pull/166) which was thought to be compatible seems to be a breaking change. In particular, one used to be able to differentiate the result of
Discard()
fromLogger{}
. After this change, those are the same. We are considering how to address this, but do not currently plan to revert this change. Apologies!What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.3...v1.2.4
v1.2.3
Compare Source
This is a minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.2...v1.2.3
v1.2.2
Compare Source
Bugfix release
MaxLogDepth
which controls how many levels of nested fields (e.g. a struct that contains a struct that contains a struct, etc.) it may log. Every time it finds a struct, slice, array, or map the depth is increased by one. When the maximum is reached, the value will be converted to a string indicating that the max depth has been exceeded. If this field is not specified, a default value will be used.v1.2.1
Compare Source
This is a minor bugfix release.
Error()
semantics. 1) Error messages are always printed (they do not followV()
) and theerror
argument may be nil.RenderValuesHook
func would save the "cooked" result, so repeated calls toWithValues()
would not merge properly.v1.2.0
Compare Source
This release has several bug fixes and feature improvements.
logr.Marshaler
interface for types which want to control how they get loggedfmt.Stringer
anderror
interfaces on values which implement themjson
struct tags (all except "string")json
packageencoding.TextMarshaler
for map keysgo doc
enhancementsv1.1.0
Compare Source
This release has several bugfixes and feature improvements.
WithCallDepth()
calls.GetSink()
andSetSink()
for customWithSomething(logr, something)
integrations.CallStackHelperLogSink
interface so that implementations which have a function to flag helper functions (e.g.testing.T
hasHelper()
) can attribute callers correctly. Log helper functions should prefer to useWithCallStackHelper()
insteadWithCallDepth(1)
for maximum reach. Note the signature ofWithCallStackHelper()
- the caller must ALSO call the returned function.LogTimestamp
option.funcr.Formatter
in other logger implementations. Used intesting.NewTestLogger()
NewTestLogger()
LogTimestamp
andVerbosity
inNewTestLoggerWithOptions()
v1.0.0
Compare Source
This is the first logged release. Major changes (including breaking changes)
have occurred since earlier tags.
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.