chore(deps): update all non-major dependencies #303
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
cb59b68
to
153eae9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
77e8c5f
to
b5dde70
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
b5dde70
to
6d87647
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
6e3aa24
to
179d9f5
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
179d9f5
to
6d34a5e
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.13.2->v1.13.3v1.23.1->v1.24.0v1.25.5->v1.26.2v1.16.4->v1.16.13v1.24.3->v1.25.5v1.27.3->v1.28.6v1.22.3->v1.23.7v1.25.4->v1.26.6v1.13.2->v1.13.3v1.3.0->v1.4.11.21.4->1.21.5v0.28.4->v0.29.0v0.28.4->v0.29.0v0.28.4->v0.29.0cf03d44->b307cd5Release Notes
cert-manager/cert-manager (cert-manager/cert-manager)
v1.13.3Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
This patch release contains fixes for the following security vulnerabilities in the cert-manager-controller:
GO-2023-2334: Decryption of malicious PBES2 JWE objects can consume unbounded system resources.If you use ArtifactHub Security report or trivy, this patch will also silence the following warning about a vulnerability in code which is imported but not used by the cert-manager-controller:
CVE-2023-47108: DoS vulnerability inotelgrpcdue to unbound cardinality metrics.An ongoing security audit of cert-manager suggested some changes to the webhook code to mitigate DoS attacks, and these are included in this patch release.
Changes
Bug or Regression
>= 3MiB. This is to mitigate DoS attacks that attempt to crash the webhook process by sending large requests that exceed the available memory. (#6507, @inteon)ReadHeaderTimeoutin allhttp.Serverinstances. (#6538, @wallrj)otel,docker, andjoseto fix CVE alerts. See GHSA-8pgv-569h-w5rw, GHSA-jq35-85cj-fj4p, and GHSA-2c7c-3mj9-8fqh. (#6514, @inteon)Dependencies
Added
Nothing has changed.
Changed
cloud.google.com/go/firestore:v1.11.0 → v1.12.0cloud.google.com/go:v0.110.6 → v0.110.7github.com/felixge/httpsnoop:v1.0.3 → v1.0.4github.com/go-jose/go-jose/v3:v3.0.0 → v3.0.1github.com/go-logr/logr:v1.2.4 → v1.3.0github.com/golang/glog:v1.1.0 → v1.1.2github.com/google/go-cmp:v0.5.9 → v0.6.0go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc:v0.45.0 → v0.46.0go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp:v0.44.0 → v0.46.0go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc:v1.19.0 → v1.20.0go.opentelemetry.io/otel/exporters/otlp/otlptrace:v1.19.0 → v1.20.0go.opentelemetry.io/otel/metric:v1.19.0 → v1.20.0go.opentelemetry.io/otel/sdk:v1.19.0 → v1.20.0go.opentelemetry.io/otel/trace:v1.19.0 → v1.20.0go.opentelemetry.io/otel:v1.19.0 → v1.20.0go.uber.org/goleak:v1.2.1 → v1.3.0golang.org/x/sys:v0.13.0 → v0.14.0google.golang.org/genproto/googleapis/api:f966b18 → b8732ecgoogle.golang.org/genproto:f966b18 → b8732ecgoogle.golang.org/grpc:v1.58.3 → v1.59.0Removed
Nothing has changed.
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)
v1.24.0Compare Source
v1.23.5Compare Source
v1.23.4Compare Source
v1.23.3Compare Source
v1.23.2Compare Source
go-logr/logr (github.com/go-logr/logr)
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan 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
kubernetes/api (k8s.io/api)
v0.29.0Compare Source
v0.28.5Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.29.0Compare Source
v0.28.5Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.29.0Compare Source
v0.28.5Compare Source
Configuration
📅 Schedule: Branch creation - "after 9am on Wednesday,before 12pm on Wednesday" 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 Mend Renovate. View repository job log here.