NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #110 by repository stars
Last release 7 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 5 months
Nearly every release is documented
notes for 15 of 15 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
109 releases · first in 2016
[#725][]: Add zapcore.OmitKey to omit keys in an EncoderConfig.
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#657][]: Fix MapObjectEncoder.AppendByteString not adding value as a string.
Bugfixes:
MapObjectEncoder.AppendByteString not adding value as a
string.Enhancements:
zaptest.WrapOptions to wrap zap.Option for creating test
loggers.Thanks to @iaroslav-ciupin, @lelenanam, @joa, @NWilson for their contributions to this release.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#614][]: MapObjectEncoder should not ignore empty slices.
Bugfixes:
[#602][]: Reduce number of allocations when logging with reflection.
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#508][]: Make log level configurable when redirecting the standard library's logger.
Enhancements:
*testing.TB.zapcore.Field to clean up GoDoc.Bugfixes:
go.uber.org/zap/buffer.Thanks to @DiSiqueira and @djui for their contributions to this release.
Nothing published for this version
[#504][]: Store strings when using AddByteString with the map encoder.
Bugfixes:
[#487][]: Add NewStdLogAt, which extends NewStdLog by allowing the user to specify the level of the logged messages.
Enhancements:
NewStdLogAt, which extends NewStdLog by allowing the user
to specify the level of the logged messages.[#491][]: Omit zap stack frames from stacktraces.
Nothing published for this version
[#460][] and [#470][]: Support errors produced by go.uber.org/multierr.
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#435][]: Support a variety of case conventions when unmarshaling levels.
Nothing published for this version
This release adds a few small features and is fully backward-compatible.
This release adds a few small features and is fully backward-compatible.
Enhancements:
This release adds an enhancement to zap's testing helpers as well as the ability to marshal an AtomicLevel. It is fully backward-compatible.
This release adds an enhancement to zap's testing helpers as well as the ability to marshal an AtomicLevel. It is fully backward-compatible.
Enhancements:
This release adds a gRPC compatibility wrapper. It is fully backward-compatible.
This release adds a gRPC compatibility wrapper. It is fully backward-compatible.
Enhancements:
zapgrpc package that wraps zap's Logger and implements
grpclog.Logger.This release fixes two bugs and adds some enhancements to zap's testing helpers. It is fully backward-compatible.
This release fixes two bugs and adds some enhancements to zap's testing helpers. It is fully backward-compatible.
Bugfixes:
Enhancements:
Thanks to @moitias for contributing to this release.
This is zap's first stable release. All exported APIs are now final, and no further breaking changes will be made in the 1.x release series. Anyone us…
This is zap's first stable release. All exported APIs are now final, and no
further breaking changes will be made in the 1.x release series. Anyone using a
semver-aware dependency manager should now pin to ^1.
Breaking changes:
[]byte to string.Sync methods to zapcore.Core,
zap.Logger, and zap.SugaredLogger.testutils package to zaptest, which is less likely to
clash with other testing helpers.Bugfixes:
zapcore.NewCore, which allows zap to
work with concurrency-safe WriteSyncer implementations.fsync standard out on Linux
systems.Enhancements:
Config.CombineWriteSyncers, a convenience function to tee multiple
WriteSyncers and lock the result.zaptest/observer. This makes it
easier for particularly punctilious users to unit test their application's
logging.Thanks to @suyash, @htrendev, @flisky, @Ulexus, and @skipor for their contributions to this release.
This is the third release candidate for zap's stable release. There are no breaking changes.
This is the third release candidate for zap's stable release. There are no breaking changes.
Bugfixes:
zap.Any are now correctly treated as binary blobs
rather than []uint8.Enhancements:
log.Logger instance.Thanks to @ansel1 and @suyash for their contributions to this release.
Nothing published for this version
Nothing published for this version
This is the second release candidate for zap's stable release. It includes two breaking changes.
This is the second release candidate for zap's stable release. It includes two breaking changes.
Breaking changes:
#316: Zap's global loggers are now fully concurrency-safe
(previously, users had to ensure that ReplaceGlobals was called before the
loggers were in use). However, they must now be accessed via the L() and
S() functions. Users can update their projects with
gofmt -r "zap.L -> zap.L()" -w .
gofmt -r "zap.S -> zap.S()" -w .
#309 and #317: RC1 was mistakenly shipped with invalid JSON and YAML struct tags on all config structs. This release fixes the tags and adds static analysis to prevent similar bugs in the future.
Bugfixes:
log output now
correctly reports the logger's caller.Enhancements:
github.com/pkg/errors.New(nil) continues to return a no-op logger, NewNop() is
now preferred. Users can update their projects with gofmt -r 'zap.New(nil) -> zap.NewNop()' -w ..github.com/uber-go/zap now returns a
more informative error.Thanks to @skipor and @chapsuk for their contributions to this release.
Nothing published for this version
This is the first release candidate for zap's stable release. There are multiple breaking changes and improvements from the pre-release version. Most…
This is the first release candidate for zap's stable release. There are multiple breaking changes and improvements from the pre-release version. Most notably:
zap package. Code relevant
largely to extension authors is now in the zapcore package.zapcore.Core type makes it easy for third-party packages to use zap's
internals but provide a different user-facing API.Logger is now a concrete type instead of an interface.L and S are included.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This is a minor version, tagged to allow users to pin to the pre-1.0 APIs and upgrade at their leisure. Since this is the first tagged release, there
This is a minor version, tagged to allow users to pin to the pre-1.0 APIs and upgrade at their leisure. Since this is the first tagged release, there are no backward compatibility concerns and all functionality is new.
Early zap adopters should pin to the 0.1.x minor version until they're ready to upgrade to the upcoming stable release.
This is a minor version, tagged to allow users to pin to the pre-1.0 APIs and upgrade at their leisure. Since this is the first tagged release, there are no backward compatibility concerns and all functionality is new.
Early zap adopters should pin to the 0.1.x minor version until they're ready to upgrade to the upcoming stable release.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →