Bump go.uber.org/zap from 1.19.1 to 1.24.0

[dependabot]

Bumps go.uber.org/zap from 1.19.1 to 1.24.0.

Release notes

Sourced from go.uber.org/zap's releases.

v1.24.0

Enhancements:

• #1148[]: Add Level to both Logger and SugaredLogger that reports the current minimum enabled log level.
• #1185[]: SugaredLogger turns errors to zap.Error automatically.

Thanks to @​Abirdcfly, @​craigpastro, @​nnnkkk7, and @​sashamelentyev for their contributions to this release.

#1148: uber-go/zap#1148 #1185: uber-go/zap#1185

v1.23.0

Enhancements:

• #1147[]: Add a zapcore.LevelOf function to determine the level of a LevelEnabler or Core.
• #1155[]: Add zap.Stringers field constructor to log arrays of objects that implement String() string.

#1147: uber-go/zap#1147 #1155: uber-go/zap#1155

v1.22.0

Enhancements:

• #1071[]: Add zap.Objects and zap.ObjectValues field constructors to log arrays of objects. With these two constructors, you don't need to implement zapcore.ArrayMarshaler for use with zap.Array if those objects implement zapcore.ObjectMarshaler.
• #1079[]: Add SugaredLogger.WithOptions to build a copy of an existing SugaredLogger with the provided options applied.
• #1080[]: Add *ln variants to SugaredLogger for each log level. These functions provide a string joining behavior similar to fmt.Println.
• #1088[]: Add zap.WithFatalHook option to control the behavior of the logger for Fatal-level log entries. This defaults to exiting the program.
• #1108[]: Add a zap.Must function that you can use with NewProduction or NewDevelopment to panic if the system was unable to build the logger.
• #1118[]: Add a Logger.Log method that allows specifying the log level for a statement dynamically.

Thanks to @​cardil, @​craigpastro, @​sashamelentyev, @​shota3506, and @​zhupeijun for their contributions to this release.

#1071: uber-go/zap#1071 #1079: uber-go/zap#1079 #1080: uber-go/zap#1080 #1088: uber-go/zap#1088

... (truncated)

Changelog

Sourced from go.uber.org/zap's changelog.

1.24.0 (30 Nov 2022)

Enhancements:

• #1148[]: Add Level to both Logger and SugaredLogger that reports the current minimum enabled log level.
• #1185[]: SugaredLogger turns errors to zap.Error automatically.

Thanks to @​Abirdcfly, @​craigpastro, @​nnnkkk7, and @​sashamelentyev for their contributions to this release.

#1148: https://github.coml/uber-go/zap/pull/1148 #1185: https://github.coml/uber-go/zap/pull/1185

1.23.0 (24 Aug 2022)

Enhancements:

• #1147[]: Add a zapcore.LevelOf function to determine the level of a LevelEnabler or Core.
• #1155[]: Add zap.Stringers field constructor to log arrays of objects that implement String() string.

#1147: uber-go/zap#1147 #1155: uber-go/zap#1155

1.22.0 (8 Aug 2022)

Enhancements:

• #1071[]: Add zap.Objects and zap.ObjectValues field constructors to log arrays of objects. With these two constructors, you don't need to implement zapcore.ArrayMarshaler for use with zap.Array if those objects implement zapcore.ObjectMarshaler.
• #1079[]: Add SugaredLogger.WithOptions to build a copy of an existing SugaredLogger with the provided options applied.
• #1080[]: Add *ln variants to SugaredLogger for each log level. These functions provide a string joining behavior similar to fmt.Println.
• #1088[]: Add zap.WithFatalHook option to control the behavior of the logger for Fatal-level log entries. This defaults to exiting the program.
• #1108[]: Add a zap.Must function that you can use with NewProduction or NewDevelopment to panic if the system was unable to build the logger.
• #1118[]: Add a Logger.Log method that allows specifying the log level for a statement dynamically.

Thanks to @​cardil, @​craigpastro, @​sashamelentyev, @​shota3506, and @​zhupeijun for their contributions to this release.

#1071: uber-go/zap#1071 #1079: uber-go/zap#1079 #1080: uber-go/zap#1080 #1088: uber-go/zap#1088

... (truncated)

Commits

• a55bdc3 Release v1.24.0 (#1208)
• ed5598a Use ReplaceAll instead of Replace with -1 pos arg (#1195)
• da406e3 Chore: Fix deprecation docs and links (#1193)
• 9b86a50 SugaredLogger: Turn error into zap.Error (#1185)
• 9137e0e go.mod: Bump go directive to 1.19 (#1181)
• 7cabba7 Open absolute paths as files, limited Windows support (#1159)
• 7681a0a Export objectMarshalerPtr (#1171)
• 9abd14b chore: remove duplicate word in comments (#1169)
• eae3743 Logger, SugaredLogger: Add Level method (#1148)
• 0d6a75b tests: assert.Error/Contains => assert.ErrorContains (#1158)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[knative-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dprotaso]

/ok-to-test

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.02% 🎉

Comparison is base (1ea9b2d) 81.75% compared to head (83afff2) 81.78%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2774      +/-   ##
==========================================
+ Coverage   81.75%   81.78%   +0.02%     
==========================================
  Files         167      167              
  Lines       10201    10201              
==========================================
+ Hits         8340     8343       +3     
+ Misses       1614     1612       -2     
+ Partials      247      246       -1     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nak3]

@dependabot rebase

[jarias-lfx]

/easycla

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[nak3]

/lgtm
/approve

[knative-prow-robot]

rebase

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nak3]

@dependabot recreate

[nak3]

/retest

[nak3]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], nak3

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nak3]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment