Update module github.com/go-logr/zapr to v1 - autoclosed #247
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
force-pushed
the
renovate/github.com-go-logr-zapr-1.x
branch
3 times, most recently
from
3e2187c to
c7fe144
Compare
renovate
bot
force-pushed
the
renovate/github.com-go-logr-zapr-1.x
branch
from
c7fe144 to
61bd493
Compare
renovate
bot
force-pushed
the
renovate/github.com-go-logr-zapr-1.x
branch
from
61bd493 to
f59e383
Compare
renovate
bot
force-pushed
the
renovate/github.com-go-logr-zapr-1.x
branch
from
f59e383 to
d9a196d
Compare
renovate
bot
force-pushed
the
renovate/github.com-go-logr-zapr-1.x
branch
from
d9a196d to
d9569a1
Compare
renovate
bot
changed the title
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:
v0.4.0->v1.3.0Release Notes
go-logr/zapr (github.com/go-logr/zapr)
v1.3.0Compare Source
This release adds support for slog. zapr implements
slogr.SlogSinkand therefore can be used throughslogr.NewSlogHandleras backend for slog.What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.4...v1.3.0
v1.2.4Compare Source
What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.3...v1.2.4
v1.2.3Compare Source
What's Changed
Full Changelog: go-logr/zapr@v1.2.2...v1.2.3
v1.2.2Compare Source
Update to logr v1.2.2
v1.2.0Compare Source
This release has some improvements:
v1.1.0Compare Source
This release has bugfixes and feature improvements.
NewLoggerWithOptions()function can be used to customize the behavior of the logger:LogInfoLevel: a field with a configurable name can be added for the numeric verbosity level of info messages. Error messages have no verbosity and thus are logged without that field.DPanicOnBugs: by default, zapr callszap.DPanicfor invalid log calls to emit an error message with details about the invalid call and, depending on the configuration of the zap logger, cause a panic. This can be disabled in zapr.AllowZapFields: passing a zap field instead of a key/value pair is non-portable and considered an error by default. Users who want to do that because they know that the underlyingLoggeris based on zap can disable that check.ErrorKey: the default "error" name forErrormessages can be overridden.zapr.go.V()range (up toV(127))v1.0.0Compare Source
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.