Renovate: Update External dependencies #119
Open
Conversation
This file contains hidden or 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
requested review from
IvoGoman,
abhijith-darshan,
onuryilmaz and
uwe-mayer
as code owners
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/external-dependencies
branch
2 times, most recently
from
be6017d to
8a5e2d7
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/external-dependencies
branch
3 times, most recently
from
d5a8083 to
2601f53
Compare
renovate
bot
force-pushed
the
renovate/external-dependencies
branch
2 times, most recently
from
2a2707d to
71bf5b1
Compare
renovate
bot
force-pushed
the
renovate/external-dependencies
branch
from
71bf5b1 to
07ea95e
Compare
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:
v2.1.8→v2.2.0v1.18.2→v1.19.2v1.20.0→v1.22.0v2.23.4→v2.27.5v1.38.0→v1.39.0v1.23.0→v1.23.2v1.27.0→v1.27.1v0.33.4→v0.33.7v0.33.4→v0.33.7v0.33.4→v0.33.7v0.21.0→v0.23.0Release Notes
sapcc/git-cert-shim (ghcr.io/sapcc/git-cert-shim)
v2.2.0Compare Source
cert-manager/cert-manager (github.com/cert-manager/cert-manager)
v1.19.2Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
We updated Go to fix some vulnerabilities in the standard library.
Changes since
v1.19.1Bug or Regression
CVE-2025-47914andCVE-2025-58181which were reported by Trivy. (#8283, @SgtCoDFish)v1.25.5to fixCVE-2025-61727andCVE-2025-61729(#8294, @wallrj-cyberark)global.nodeSelectorto helm chart to perform amergeand allow for a singlenodeSelectorto be set across all services. (#8233, @cert-manager-bot)Other (Cleanup or Flake)
golang/x/crypto(#8270, @SgtCoDFish)v1.19.1Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
We reverted the CRD-based API defaults for
Certificate.Spec.IssuerRefandCertificateRequest.Spec.IssuerRefafter they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager1.20.We fixed a bug that caused certificates to be re-issued unexpectedly if the
issuerRefkind or group was changed to one of the "runtime" default values.We upgraded Go to
1.25.3to address the following security vulnerabilities:CVE-2025-61724,CVE-2025-58187,CVE-2025-47912,CVE-2025-58183,CVE-2025-61723,CVE-2025-58186,CVE-2025-58185,CVE-2025-58188, andCVE-2025-61725.Changes since
v1.19.0:Bug or Regression
issuerRefof a Certificate was omitted, upgrading to1.19.xincorrectly caused the certificate to be renewed (#8175, @cert-manager-bot)v1.19.0Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.
Changes since
v1.18.0:Feature
global.nodeSelectorto helm chart to allow for a singlenodeSelectorto be set across all services. (#7818, @StingRayZA)pathTypeExactin ACME HTTP01 Ingress challenge solvers. (#7795, @sspreitzer)applyconfigurationsallowing clients to make type-safe server-side apply requests for cert-manager resources. (#7866, @erikgb)certmanager_certificate_challenge_statusPrometheus metric. (#7736, @hjoshi123)protocolfield forrfc2136DNS01 provider (#7881, @hjoshi123)hostUsersflag to all pods. Not set by default. (#7973, @hjoshi123)--acme-http01-solver-resource-*settings. (#7972, @lunarwhite)CAInjectorMergingfeature has been promoted to BETA and is now enabled by default (#8017, @ThatsMrTalbot)certificatemetrics to the collector approach. (#7856, @hjoshi123)Bug or Regression
error waiting for authorization(#7796, @hjoshi123)class,ingressClassName,name) are specified simultaneously (#8021, @lunarwhite)global.rbac.disableHTTPChallengesRoleHelm option. (#7836, @inteon)pathlabel of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. (#8109, @mladen-rusev-cyberark)ingress-nginxin E2E tests to ensure compatibility (#7792, @wallrj)Other (Cleanup or Flake)
tokenrequestRoleBinding resource to improve consistency (#7761, @lunarwhite)maps.Copyfor cleaner map handling (#8092, @quantpoet)vault-client-goto the newvault/apiclient. (#8059, @armagankaratosun)v1.18.4Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
We updated Go to fix some vulnerabilities in the standard library.
Changes since
v1.18.3Bug or Regression
CVE-2025-47914andCVE-2025-58181which were reported by Trivy. (#8282, @SgtCoDFish)v1.24.11to fixCVE-2025-61727andCVE-2025-61729(#8295, @wallrj-cyberark)Other (Cleanup or Flake)
golang/x/crypto(#8271, @SgtCoDFish)v1.18.3Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.
Changes since
v1.18.2:Bug or Regression
Other (Cleanup or Flake)
hashicorp/vault (github.com/hashicorp/vault/api)
v1.21.0Compare Source
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.27.5Compare Source
2.27.5
Fixes
Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory
v2.27.4Compare Source
2.27.4
Fixes
59bc751]v2.27.3Compare Source
2.27.3
Fixes
report exit result in case of failure [
1c9f356]fix data race [
ece19c8]v2.27.2Compare Source
2.27.2
Fixes
a69113a]Maintenance
a99c6e0]f993df5]v2.27.1Compare Source
2.27.1
Fixes
606c1cb]a6463b3]v2.27.0Compare Source
2.27.0
Features
Transforming Nodes during Tree Construction
This release adds support for
NodeArgsTransformers that can be registered withAddTreeConstructionNodeArgsTransformer.These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.
Learn more here.
Spec Prioritization
A new
SpecPriority(int)decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specsLearn more here.
Maintenance
1333dae]17ae63e]v2.26.0Compare Source
2.26.0
Features
Ginkgo can now generate json-formatted reports that are compatible with the
go testjson format. Useginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.v2.25.3Compare Source
2.25.3
Fixes
f01aed1]v2.25.2Compare Source
2.25.2
Fixes
Add github output group for progress report content
Maintenance
Bump Gomega
v2.25.1Compare Source
2.25.1
Fixes
10866d3]2e42cff]v2.25.0Compare Source
2.25.0
AroundNodeThis release introduces a new decorator to support more complex spec setup usecases.
AroundNoderegisters a function that runs before each individual node. This is considered a more advanced decorator.Please read the docs for more information and some examples.
Allowed signatures:
AroundNode(func())-funcwill be called before the node is run.AroundNode(func(ctx context.Context) context.Context)-funccan wrap the passed in context and return a new one which will be passed on to the node.AroundNode(func(ctx context.Context, body func(ctx context.Context)))-ctxis the context for the node andbodyis a function that must be called to run the node. This gives you complete control over what runs before and after the node.Multiple
AroundNodedecorators can be applied to a single node and they will run in the order they are applied.Unlike setup nodes like
BeforeEachandDeferCleanup,AroundNodeis guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can callruntime.LockOSThread()in theAroundNodeto ensure that the node runs on a single thread).Since
AroundNodeallows you to modify the context you can also useAroundNodeto implement shared setup that attaches values to the context.If applied to a container,
AroundNodewill run before every node in the container. Including setup nodes likeBeforeEachandDeferCleanup.AroundNodecan also be applied toRunSpecsto run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.v2.24.0Compare Source
2.24.0
Features
Specs can now be decorated with (e.g.)
SemVerConstraint("2.1.0")andginkgo --sem-ver-filter="2.1.1"will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @Icarus9913 for the PR.Fixes
3f5d379]. fixes #1582Maintenance
Numerous dependency bumps and documentation fixes
onsi/gomega (github.com/onsi/gomega)
v1.39.0Compare Source
1.39.0
Features
Add
MatchErrorStrictlywhich only passes iferrors.Is(actual, expected)returns true.MatchError, by contrast, will fallback to string comparison.v1.38.3Compare Source
1.38.3
Fixes
make string formatitng more consistent for users who use format.Object directly
v1.38.2Compare Source
1.38.2
c404969]v1.38.1Compare Source
1.38.1
Fixes
Numerous minor fixes and dependency bumps
prometheus/client_golang (github.com/prometheus/client_golang)
v1.23.2: - 2025-09-05Compare Source
This release is made to upgrade to prometheus/common v0.66.1, which drops the dependencies github.com/grafana/regexp and go.uber.org/atomic and replaces gopkg.in/yaml.v2 with go.yaml.in/yaml/v2 (a drop-in replacement). There are no functional changes.
All Changes
Full Changelog: prometheus/client_golang@v1.23.1...v1.23.2
v1.23.1: - 2025-09-04Compare Source
This release is made to be compatible with a backwards incompatible API change in prometheus/common v0.66.0. There are no functional changes.
All Changes
Full Changelog: prometheus/client_golang@v1.23.0...v1.23.1
uber-go/zap (go.uber.org/zap)
v1.27.1Compare Source
Enhancements:
Objectfrom panicking on nilsWithLazy.Thanks to @rabbbit, @alshopov, @jquirke, @arukiidou for their contributions to this release.
kubernetes/api (k8s.io/api)
v0.33.7Compare Source
v0.33.6Compare Source
v0.33.5Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.33.7Compare Source
v0.33.6Compare Source
v0.33.5Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.33.7Compare Source
v0.33.6Compare Source
v0.33.5Compare Source
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)
v0.23.0Compare Source
🔆 Highlights
GetEventRecorderForrequires updating your rbac for events to use theevents.k8s.ioapiGroup rather than the `` (core) apiGroupbuilder.WebhookManagedBy(mgr).For(&corev1.Deployment{})has to be changed tobuilder.WebhookManagedBy(mgr, &appsv1.Deployment{})runtime.Object, for example fromValidateCreate(ctx context.Context, obj runtime.Object) (admission.Warnings, error)toValidateCreate(ctx context.Context, obj *appsv1.Deployment) (admission.Warnings, error)✨ Features
🐛 Bugfixes
waitermanipulation by @fossedihelm in #3368🌱 Other
sorttoslicespackage by @dongjiang1989 in #3370📖 Documentation
README.md's compatibility matrix forv0.22.x. by @renormalize in #3392Dependencies
Added
Changed
bda5523→078029d5ec99f8→9bdfabea0af3ef→200df9985fd79d→ec3ebc5f3f2b99→589584f4c0f3b2→bc988d5cfa47c3→2d32026Removed
New Contributors
Configuration
📅 Schedule: Branch creation - "before 8am on Friday" (UTC), 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 was generated by Mend Renovate. View the repository job log.