Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update module github.com/go-logr/logr to v1.2.4 #36

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

plural-renovate[bot]
Copy link
Contributor

@plural-renovate plural-renovate bot commented Nov 10, 2022

This PR contains the following updates:

Package Type Update Change
github.com/go-logr/logr require patch v1.2.0 -> v1.2.4

Release Notes

go-logr/logr (github.com/go-logr/logr)

v1.2.4

Compare Source

This is a collection of small bugfixes and documentation updates.

NOTE: A change (https://github.com/go-logr/logr/pull/166) which was thought to be compatible seems to be a breaking change. In particular, one used to be able to differentiate the result of Discard() from Logger{}. After this change, those are the same. We are considering how to address this, but do not currently plan to revert this change. Apologies!

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.2.3...v1.2.4

v1.2.3

Compare Source

This is a minor release.

What's Changed

New Contributors

Full Changelog: go-logr/logr@v1.2.2...v1.2.3

v1.2.2

Compare Source

Bugfix release

  • funcr: Add a new Option MaxLogDepth which controls how many levels of nested fields (e.g. a struct that contains a struct that contains a struct, etc.) it may log. Every time it finds a struct, slice, array, or map the depth is increased by one. When the maximum is reached, the value will be converted to a string indicating that the max depth has been exceeded. If this field is not specified, a default value will be used.

v1.2.1

Compare Source

This is a minor bugfix release.

  • logr: Clarify the Error() semantics. 1) Error messages are always printed (they do not follow V()) and the error argument may be nil.
  • funcr: When using RenderValuesHook func would save the "cooked" result, so repeated calls to WithValues() would not merge properly.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@plural-renovate plural-renovate bot changed the title Update module github.com/go-logr/logr to v1.2.3 fix(deps): update module github.com/go-logr/logr to v1.2.3 Nov 10, 2022
@davidspek davidspek added the dependencies Pull requests that update a dependency file label Nov 27, 2022
@plural-renovate plural-renovate bot changed the title fix(deps): update module github.com/go-logr/logr to v1.2.3 fix(deps): update module github.com/go-logr/logr to v1.2.4 Mar 30, 2023
@plural-renovate plural-renovate bot force-pushed the renovate/github.com-go-logr-logr-1.2.x branch from 5cb9268 to af4e370 Compare March 30, 2023 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant