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.

Sign up for GitHub

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

Jump to bottom

Update module github.com/go-logr/logr to v1 #45

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

Update module github.com/go-logr/logr to v1 #45

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-logr/logr v0.4.0 -> v1.4.1 age adoption passing confidence

Release Notes

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

v1.4.1

Compare Source

What's Changed

Full Changelog: go-logr/logr@v1.4.0...v1.4.1

v1.4.0

Compare Source

This release dramatically improves interoperability with Go's log/slog package. In particular, logr.NewContext and logr.NewContextWithSlogLogger use the same context key, which allows logr.FromContext and logr.FromContextAsSlogLogger to return logr.Logger or *slog.Logger respectively, including transparently converting each to the other as needed.

Functions logr/slogr.NewLogr and logr/slogr.ToSlogHandler have been superceded by logr.FromSlogHandler and logr.ToSlogHandler respectively, and type logr/slogr.SlogSink has been superceded by logr.SlogSink. All of the old names in logr/slogr remain, for compatibility.

Package logr/funcr now supports logr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being that funcr handles the timestamp itself).

Users who have a logr.Logger and need a *slog.Logger can call slog.New(logr.ToSlogHandler(...)) and all output will go through the same stack.

Users who have a *slog.Logger or slog.Handler can call logr.FromSlogHandler(...) and all output will go through the same stack.

What's Changed
New Contributors

Full Changelog: go-logr/logr@v1.3.0...v1.4.0

v1.3.0

Compare Source

This release adds support for slog in a new, self-contained logr/slogr package. Implementers of a logr.LogSink are encouraged, but not required, to extend their implementation to improve the quality of log output coming from a slog API call.

Breaking change: the call depth for LogSink.Enabled when called via Logger.Enabled was fixed to be the same as for other call paths. Implementers of a LogSink who have worked around this bug will need to remove their workarounds.

Security best practices were improved. Only Go versions >= 1.18 are supported by this release.

What's Changed

New Contributors

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

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.

v1.2.0

Compare Source

This release has several bug fixes and feature improvements.

  • logr: define an optional logr.Marshaler interface for types which want to control how they get logged
  • funcr: support fmt.Stringer and error interfaces on values which implement them
  • funcr: support logging complex{64,128}
  • funcr: fix handling of typed nil when logging a struct via reflection
  • funcr: add (optional) JSON output formatting mode
  • funcr: better handling of Go's json struct tags (all except "string")
  • funcr: handle embedded types more like Go's json package
  • funcr: misc performance optimizations
  • funcr: add support for modifying or remapping key/value pairs via hook functions
  • funcr: optionally log the caller function name
  • funcr: fix escaping of strings which contain special characters like line breaks or quotation marks
  • funcr: support encoding.TextMarshaler for map keys
  • funcr: allow customization of the timestamp format
  • funcr: improved testing
  • link to zerologr at its new location in the go-logr organization
  • various documentation and go doc enhancements

v1.1.0

Compare Source

This release has several bugfixes and feature improvements.

  • logr: fix incremental WithCallDepth() calls.
  • logr: expose the LogSink via GetSink() and SetSink() for custom WithSomething(logr, something) integrations.
  • logr: add an optional CallStackHelperLogSink interface so that implementations which have a function to flag helper functions (e.g. testing.T has Helper()) can attribute callers correctly. Log helper functions should prefer to use WithCallStackHelper() instead WithCallDepth(1) for maximum reach. Note the signature of WithCallStackHelper() - the caller must ALSO call the returned function.
  • funcr: add a LogTimestamp option.
  • funcr: support embedding a funcr.Formatter in other logger implementations. Used in testing.NewTestLogger()
  • testing: proper caller attribution when using NewTestLogger()
  • testing: enable options for LogTimestamp and Verbosity in NewTestLoggerWithOptions()
  • misc: Godoc clarifications

v1.0.0

Compare Source

This is the first logged release. Major changes (including breaking changes)
have occurred since earlier tags.

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 Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/github.com-go-logr-logr-1.x branch from 005b931 to 0f4fc2b Compare December 21, 2023 08:55
@renovate renovate bot force-pushed the renovate/github.com-go-logr-logr-1.x branch from 0f4fc2b to 8a0da87 Compare December 22, 2023 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants