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.4.1 #272

Merged
merged 1 commit into from
Feb 28, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 21, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-logr/logr v1.3.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


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 requested a review from dergeberl as a code owner December 21, 2023 10:10
@renovate renovate bot changed the title fix(deps): update module github.com/go-logr/logr to v1.4.0 fix(deps): update module github.com/go-logr/logr to v1.4.1 Dec 21, 2023
@renovate renovate bot force-pushed the renovate/gh.neting.cc-go-logr-logr-1.x branch from 7526e21 to 8bd3f41 Compare December 21, 2023 23:03
@renovate renovate bot force-pushed the renovate/gh.neting.cc-go-logr-logr-1.x branch 4 times, most recently from 799f451 to 6f19dbd Compare January 24, 2024 13:59
@renovate renovate bot force-pushed the renovate/gh.neting.cc-go-logr-logr-1.x branch 3 times, most recently from 6493458 to 26f2f5c Compare February 14, 2024 15:10
@renovate renovate bot force-pushed the renovate/gh.neting.cc-go-logr-logr-1.x branch from 26f2f5c to 2ae5f85 Compare February 21, 2024 12:13
@renovate renovate bot force-pushed the renovate/gh.neting.cc-go-logr-logr-1.x branch from 2ae5f85 to 75c5f4a Compare February 28, 2024 08:28
@Kumm-Kai Kumm-Kai merged commit 13d35e0 into main Feb 28, 2024
1 check passed
@Kumm-Kai Kumm-Kai deleted the renovate/gh.neting.cc-go-logr-logr-1.x branch February 28, 2024 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant