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.2 #20

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 23, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-logr/logr v1.2.4 -> v1.4.2 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v1.4.2

Compare Source

What's Changed

Dependencies:

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

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


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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Oct 23, 2023
@renovate renovate bot changed the title fix(deps): update module github.com/go-logr/logr to v1.2.4 fix(deps): update module github.com/go-logr/logr to v1.3.0 Oct 28, 2023
@renovate renovate bot force-pushed the renovate/git.luolix.top-go-logr-logr-1.x branch from b9a1414 to c9671cc Compare October 28, 2023 08:27
@renovate renovate bot changed the title fix(deps): update module github.com/go-logr/logr to v1.3.0 fix(deps): update module github.com/go-logr/logr to v1.4.1 Dec 22, 2023
@renovate renovate bot force-pushed the renovate/git.luolix.top-go-logr-logr-1.x branch from c9671cc to 35e0709 Compare December 22, 2023 02:45
Copy link
Author

renovate bot commented Apr 22, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -d -t ./...
go: errors parsing go.mod:
go.mod:82:2: replacement module without version must be directory path (rooted or starting with . or ..)

@renovate renovate bot force-pushed the renovate/git.luolix.top-go-logr-logr-1.x branch from 35e0709 to a9fe2ea Compare April 22, 2024 14:12
@renovate renovate bot force-pushed the renovate/git.luolix.top-go-logr-logr-1.x branch from a9fe2ea to db3d5ee Compare May 22, 2024 09:19
@renovate renovate bot changed the title fix(deps): update module github.com/go-logr/logr to v1.4.1 fix(deps): update module github.com/go-logr/logr to v1.4.2 May 22, 2024
Copy link
Author

renovate bot commented May 22, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -d -t ./...
go: errors parsing go.mod:
go.mod:82:2: replacement module without version must be directory path (rooted or starting with . or ..)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
0 participants