v1.3.0

This release adds support for slog. zapr implements slogr.SlogSink and therefore can be used through slogr.NewSlogHandler as backend for slog.

What's Changed

• Added dependabot by @Neo2308 in #63
• Updated min supported version to go 1.18 by @Neo2308 in #62
• update linter config and fix issues by @pohly in #61
• Bump github.com/go-logr/logr from 1.2.4 to 1.3.0 by @dependabot in #71
• support slog by @pohly in #60

---

• Bump github.com/stretchr/testify from 1.8.0 to 1.8.4 by @dependabot in #65
• Bump actions/checkout from 2 to 3 by @dependabot in #66
• Bump actions/setup-go from 2 to 4 by @dependabot in #67
• Bump golangci/golangci-lint-action from 2 to 3 by @dependabot in #68
• Bump actions/checkout from 3 to 4 by @dependabot in #69
• Bump go.uber.org/zap from 1.24.0 to 1.25.0 by @dependabot in #64
• Bump go.uber.org/zap from 1.25.0 to 1.26.0 by @dependabot in #70

New Contributors

• @Neo2308 made their first contribution in #63
• @dependabot made their first contribution in #65

Full Changelog: v1.2.4...v1.3.0

v1.2.4

What's Changed

• Bump Go version for GH actions by @thockin in #54
• [fix]fix security yaml.v3 CVE-2022-28948 by @dongjiang1989 in #58

New Contributors

• @dongjiang1989 made their first contribution in #58

Full Changelog: v1.2.3...v1.2.4

v1.2.3

What's Changed

• handle panics in logr.Marshaler.MarshalLog by @pohly in #52

Full Changelog: v1.2.2...v1.2.3

v1.2.2

Update to logr v1.2.2

v1.2.0

This release has some improvements:

• added support for logr.Marshaler
• moved code examples to make them visible in gopkg.dev

v1.1.0

This release has bugfixes and feature improvements.

• The new 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 calls zap.DPanic for 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 underlying Logger is based on zap can disable that check.
  • ErrorKey: the default "error" name for Error messages can be overridden.
• The source code attribution of the messages for invalid log calls now refers to the actual call site instead of zapr.go.
• Various documentation enhancements and more thorough testing.
• Bump zapr dependency to 1.19.0, which supports near-arbitrary negative levels, which allows full use of logr's V() range (up to V(127))

v1.0.0+1

Bump zapr dep to 1.19.0, which supports near-arbitrary negative levels.

This corresponds to logr v1.0.0

v1.0.0

Merge pull request #28 from thockin/prep-v1

Update zapr to logr v1.0.0-rc1

v0.4.0

• Support logr.WithCallDepth()

v0.3.0

• Adds Underlier interface with GetUnderlying() which callers can use if they know the implementation and need direct access.