fix(deps): update non-minor dependencies #113
Open
+70
−27
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:
1.32.0-debian-12-r0
->1.32.1-debian-12-r1
12-debian-12-r31
->12-debian-12-r35
v1.16.2
->v1.16.3
v2.22.0
->v2.22.2
v1.36.0
->v1.36.2
v0.1.44
->v0.1.55
v0.3.45
->v0.3.64
v0.2.20
->v0.2.24
1.23.2
->1.23.5
1.23.4
->1.23.5
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
v0.32.0
->v0.32.1
a9b7c2d
->aafb269
Release Notes
cert-manager/cert-manager (github.com/cert-manager/cert-manager)
v1.16.3
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.16.3 is a patch release mainly focused around bumping dependencies to address reported CVEs: CVE-2024-45337 and CVE-2024-45338.
We don't believe that cert-manager is actually vulnerable; this release is instead intended to satisfy vulnerability scanners.
It also includes a bug fix to the new
renewBeforePercentage
field. If you were usingrenewBeforePercentage
, see PR #7421 for more information.Changes
Bug
golang.org/x/net
andgolang.org/x/crypto
to address CVE-2024-45337 and CVE-2024-45338 (#7485, @erikgb)renewBeforePercentage
to comply with its spec (#7441, @cert-manager-bot)Other
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.22.2
Compare Source
What's Changed
Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2
v2.22.1
Compare Source
2.22.1
Fixes
Fix CSV encoding
aab3da6
]c09df39
]96a80fc
]43dad69
]Maintenance
c88c634
]4df44bf
]onsi/gomega (github.com/onsi/gomega)
v1.36.2
Compare Source
Maintenance
v1.36.1
Compare Source
1.36.1
Fixes
1c6c112
]4feb9d7
]sap/admission-webhook-runtime (github.com/sap/admission-webhook-runtime)
v0.1.55
Compare Source
v0.1.54
Compare Source
v0.1.53
Compare Source
v0.1.52
Compare Source
v0.1.51
Compare Source
v0.1.50
Compare Source
v0.1.49
Compare Source
v0.1.48
Compare Source
v0.1.47
Compare Source
v0.1.46
Compare Source
v0.1.45
Compare Source
sap/component-operator-runtime (github.com/sap/component-operator-runtime)
v0.3.64
Compare Source
v0.3.63
Compare Source
v0.3.62
Compare Source
Incompatible changes
Previously, the forced re-apply of dependent objects was based on a timestamp that was coded into the object digest. As a consequence, the digest annotation of every dependent object was updated more or less every 60 minutes. Which caused problems (e.g. with crossplane).
From this release onwards, the force-re-apply mechanism is based on the new status field
status.inventory[].lastAppliedAt
.Note: YOU MUST, REALLY MUST, regenerate your component CRD when using a version of component-operator-runtime containing this release, and ship the module update together with the updated CRD!!!
v0.3.61
Compare Source
v0.3.60
Compare Source
v0.3.59
Compare Source
This release is non-functional (preparation for future work). It ships a new status field
.status.inventory[].lastAppliedAt
.v0.3.58
Compare Source
This release is a bugfix release for the
clm
cli. So far, while applying or deleting a release,clm
was aborting immediately if an error occurred. This is not very convenient. At least in some ephemeral error situations, it should behave in a more resilient way. So, with this release,clm
tries to recognise such ephemeral errors (for example 409 - Conflict responses from the API server), and retries the failing operation a couple of times.v0.3.57
Compare Source
v0.3.56
Compare Source
Enhancements
A new flag
--create-namespace
was added toclm apply
. If specified the specified release namespace will be auto-created if missing. Note that in that case, the namespace is not part of the release inventory. In particular, it will not be deleted if the component gets deleted.v0.3.55
Compare Source
This release adds a new interface
PolicyConfiguration
that component types (or their spec types) can implement:Through this interface, components can override the framework default policies that would otherwise apply. Of course, dependent resources can still override the behaviour using the well-known annotations. For easier consumption (similar to the already existing
Configuration
interfaces), there is a standard implementationPolicySpec
that components may embed into their spec).Furthermore, the semantics of the deletion policy was slightly changed:
v0.3.54
Compare Source
This release adds some new template functions to
HelmGenerator
andKustomizeGenerator
.Template functions for bitwise operations:
func bitwiseShiftLeft(by any, arg any) (uint64, error)
func bitwiseShiftRight(by any, arg any) (uint64, error)
func bitwiseAnd(args ...any) (uint64, error)
func bitwiseOr(args ...any) (uint64, error)
func bitwiseXor(args ...any) (uint64, error)
Functions for IPv4 address handling:
func parseIPv4Address(data any) (uint32, error)
func formatIPv4Address(data any) (string, error)
v0.3.53
Compare Source
v0.3.52
Compare Source
This is a bugfix release, but it slightly changes the procedure how dependent objects are reconciled. In detail:
Until now,
reconciler.Apply()
(which is what happens if a component is reconciled, not deleted) first deleted all redundant objects, that is objects which appear in the component's inventory, but are no longer part of the current manifest list. Only after all redundant objects were gone, the reconciliation of the current dependents was started. This potentially caused some deadlock situations, e.g. in component-operator. To overcome, the deletion part was shifted to the end ofreconciler.Apply()
, after the application of the current manifest list. This should not be a noticeable change. However, the completion handling still happens early (before the reconciliation of the dependents), and was slightly changed as well; for example, object deletions happening as consequence of a completion now no longer honourdelete-order
ordelete-policy
.v0.3.51
Compare Source
v0.3.50
Compare Source
v0.3.49
Compare Source
v0.3.48
Compare Source
v0.3.47
Compare Source
v0.3.46
Compare Source
sap/go-generics (github.com/sap/go-generics)
v0.2.24
Compare Source
v0.2.23
Compare Source
v0.2.22
Compare Source
v0.2.21
Compare Source
golang/go (go)
v1.23.5
v1.23.4
v1.23.3
kubernetes/api (k8s.io/api)
v0.32.1
Compare Source
kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.32.1
Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.32.1
Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.32.1
Compare Source
kubernetes/code-generator (k8s.io/code-generator)
v0.32.1
Compare Source
kubernetes/kube-aggregator (k8s.io/kube-aggregator)
v0.32.1
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.