fix(deps): update module go.uber.org/zap to v1.24.0 #18
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.21.0
->v1.24.0
Release Notes
uber-go/zap
v1.24.0
Compare Source
Enhancements:
Level
to bothLogger
andSugaredLogger
that reports thecurrent minimum enabled log level.
SugaredLogger
turns errors to zap.Error automatically.Thanks to @Abirdcfly, @craigpastro, @nnnkkk7, and @sashamelentyev for their
contributions to this release.
v1.23.0
Compare Source
Enhancements:
zapcore.LevelOf
function to determine the level of aLevelEnabler
orCore
.zap.Stringers
field constructor to log arrays of objectsthat implement
String() string
.v1.22.0
Compare Source
Enhancements:
zap.Objects
andzap.ObjectValues
field constructors to logarrays of objects. With these two constructors, you don't need to implement
zapcore.ArrayMarshaler
for use withzap.Array
if those objects implementzapcore.ObjectMarshaler
.SugaredLogger.WithOptions
to build a copy of an existingSugaredLogger
with the provided options applied.*ln
variants toSugaredLogger
for each log level.These functions provide a string joining behavior similar to
fmt.Println
.zap.WithFatalHook
option to control the behavior of thelogger for
Fatal
-level log entries. This defaults to exiting the program.zap.Must
function that you can use withNewProduction
orNewDevelopment
to panic if the system was unable to build the logger.Logger.Log
method that allows specifying the log level fora statement dynamically.
Thanks to @cardil, @craigpastro, @sashamelentyev, @shota3506, and @zhupeijun
for their contributions to this release.
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 Renovate Bot.