fix(deps): update module github.com/go-logr/logr to v1.4.1 #474
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
@renovate[bot] Image is available for testing. |
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
068eb9d to
6a07671
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
6a07671 to
e28dcc8
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
e28dcc8 to
cb85777
Compare
renovate
bot
force-pushed
the
renovate/github.com-go-logr-logr-1.x
branch
from
cb85777 to
edfb5d1
Compare
renovate
bot
changed the title
karl-johan-grahn
approved these changes
Feb 7, 2024
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.0->v1.4.1Release Notes
go-logr/logr (github.com/go-logr/logr)
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
v1.2.4Compare 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.3Compare Source
This is a minor release.
What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.2.2...v1.2.3
v1.2.2Compare Source
Bugfix release
MaxLogDepthwhich 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.1Compare Source
This is a minor bugfix release.
Error()semantics. 1) Error messages are always printed (they do not followV()) and theerrorargument may be nil.RenderValuesHookfunc would save the "cooked" result, so repeated calls toWithValues()would not merge properly.Configuration
📅 Schedule: Branch creation - "monthly" (UTC), 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.