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

chore(deps): update module github.com/go-logr/logr to v1.4.1 #9

Merged
merged 1 commit into from
Jan 20, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2024

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: Enabled.

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 a team as a code owner January 19, 2024 11:43
Copy link

github-actions bot commented Jan 19, 2024

Pull Request Test Coverage Report for Build 7593090837

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 95.302%

Totals Coverage Status
Change from base Build 7593089009: 0.0%
Covered Lines: 568
Relevant Lines: 596

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/github.com-go-logr-logr-1.x branch 5 times, most recently from 4e76637 to 1fdfc58 Compare January 20, 2024 03:30
@renovate renovate bot force-pushed the renovate/github.com-go-logr-logr-1.x branch from 1fdfc58 to 22e7149 Compare January 20, 2024 07:56
@renovate renovate bot merged commit 5311a8f into master Jan 20, 2024
7 checks passed
@renovate renovate bot deleted the renovate/github.com-go-logr-logr-1.x branch January 20, 2024 10:23
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.

0 participants