-
Notifications
You must be signed in to change notification settings - Fork 31
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
Update misc - autoclosed #151
Conversation
d408ba5
to
9426219
Compare
/retest |
7b287f6
to
0d86b61
Compare
/test mariadb-operator-build-deploy-kuttl
|
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
0d86b61
to
df0fdee
Compare
9fbdeb7
to
00c3790
Compare
00c3790
to
809bfd0
Compare
809bfd0
to
96009bb
Compare
/test mariadb-operator-build-deploy-kuttl
|
96009bb
to
6c41c61
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gibizer, openstack-k8s-ci-robot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR contains the following updates:
v1.2.4
->v1.4.1
v1.25.0
->v1.26.0
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
andlogr.NewContextWithSlogLogger
use the same context key, which allowslogr.FromContext
andlogr.FromContextAsSlogLogger
to returnlogr.Logger
or*slog.Logger
respectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLogr
andlogr/slogr.ToSlogHandler
have been superceded bylogr.FromSlogHandler
andlogr.ToSlogHandler
respectively, and typelogr/slogr.SlogSink
has been superceded bylogr.SlogSink
. All of the old names inlogr/slogr
remain, for compatibility.Package
logr/funcr
now supportslogr.SlogSink
, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncr
handles the timestamp itself).Users who have a
logr.Logger
and need a*slog.Logger
can callslog.New(logr.ToSlogHandler(...))
and all output will go through the same stack.Users who have a
*slog.Logger
orslog.Handler
can calllogr.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 alogr.LogSink
are encouraged, but not required, to extend their implementation to improve the quality of log output coming from aslog
API call.Breaking change: the call depth for
LogSink.Enabled
when called viaLogger.Enabled
was fixed to be the same as for other call paths. Implementers of aLogSink
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
uber-go/zap (go.uber.org/zap)
v1.26.0
Compare Source
Enhancements:
Dict
as aField
.WithLazy
method toLogger
which lazily evaluates the structuredcontext.
Thanks to @hhk7734, @jquirke, @cdvr1993 for their contributions to this release.
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.