Repository navigation
chore(deps): update dependencies (patch & digest) - #111
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
added
automerge
ok-to-e2e
ok-to-image
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
renovate
Bot
force-pushed
the
renovate/all-patch-and-digest-updates
branch
2 times, most recently
from
November 2, 2026 20:16
43f63b9 to
dd31077
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-and-digest-updates
branch
3 times, most recently
from
November 7, 2026 22:11
41dc850 to
3d4e67a
Compare
renovate
Bot
force-pushed
the
renovate/all-patch-and-digest-updates
branch
from
November 10, 2026 01:46
3d4e67a to
90090ae
Compare
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
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→v2.0.1v7→v7.0.1v1.21.2→v1.21.3dbcb813→8aa5831v4.39.0→v4.39.3Release Notes
actions/add-to-project
v2.0.1Compare Source
What's Changed
js-yamlto 4.3.1 and 3.15.1 to address GHSA-5p4m-2wfm-xmqj by @schustafa in #811New Contributors
Full Changelog: actions/add-to-project@v2.0.0...v2.0.1
actions/checkout
v7.0.1Compare Source
cert-manager/cert-manager (cert-manager)
v1.21.3Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.21.3 removes trust in the compromised eMudhra CA (see eMudhra Compromise). The updated base images no longer include the "emSign ECC Root CA - G3" root certificate. Go 1.26.10 also makes
crypto/x509reject certificate chains that pass through the compromised intermediates (CVE-2026-111943).It also fixes an ACME ARI renewal loop, stops the controller copying a private key from a Secret that the Certificate does not own, and quotes the proxy values in the Helm chart. It updates Go and several dependencies to fix reported security vulnerabilities.
All users should upgrade.
Changes by Kind
Bug or Regression
status.acme.ari.certIDto track issuance of new certs and re-fetch ARI from CA. This fixes a renewal loop where a stale ARI window from the previous certificate triggered repeated re-issuance until the CA rate limit was hit. (#9292, @hjoshi123)http_proxy,https_proxyandno_proxyvalues when rendering the controller Deployment env vars, so values like*.example.comno longer break the manifest. (#9407, @pujitha24)requestmanagerandissuingcontrollers now only consume the Secret named bystatus.nextPrivateKeySecretNamewhen it carries thecert-manager.io/next-private-keylabel and is owned by the Certificate, matching the invariant thekeymanagercontroller already enforces. Previously a principal able to write thecertificates/statussubresource, but not to read Secrets, could name any Secret in the namespace and have its private key copied intospec.secretName. Thekeymanagercontroller no longer creates the next private key Secret under the name instatus.nextPrivateKeySecretName. It always uses a generated name, records aNotOwnedWarning event when the field names a Secret it does not own, and repoints the field at the Secret it owns rather than deleting that Secret when the two disagree. The Secret named byspec.secretNameis never treated as a next private key Secret, even ifspec.secretTemplatelabels it as one. (#9368, @wallrj)Other (Cleanup or Flake)
golang.org/x/netto v0.60.0 to fix reported security vulnerabilities (#9451)go.opentelemetry.io/otel/exporters/otlp/otlptraceandotlptracegrpcto v1.45.0 to fix a reported security vulnerability (#9374, #9375)github/codeql-action
v4.39.3Compare Source
v4.39.2Compare Source
CODEQL_ACTION_CLEANUP_TRAP_CACHESenvironment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. TheanalyzeAction now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing thetrap-caching: falseinput to theinitAction. #4243v4.39.1Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.