Skip to content
This repository was archived by the owner on Feb 3, 2023. It is now read-only.

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2022

Bumps github.com/go-logr/zapr from 0.4.0 to 1.2.3.

Release notes

Sourced from github.com/go-logr/zapr's releases.

v1.2.3

What's Changed

Full Changelog: go-logr/zapr@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

No release notes provided.

v1.0.0+1

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

This corresponds to logr v1.0.0

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/go-logr/zapr](https://github.com/go-logr/zapr) from 0.4.0 to 1.2.3.
- [Release notes](https://github.com/go-logr/zapr/releases)
- [Commits](go-logr/zapr@v0.4.0...v1.2.3)

---
updated-dependencies:
- dependency-name: github.com/go-logr/zapr
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Feb 21, 2022
@dependabot dependabot bot requested a review from a team February 21, 2022 21:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant