generated from SAP/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 5
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
fix(deps): update non-minor dependencies #113
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/non-minor-deps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
changed the title
fix(deps): update module github.com/sap/component-operator-runtime to v0.3.46
fix(deps): update non-minor dependencies
Oct 21, 2024
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
3 times, most recently
from
October 23, 2024 22:20
130a78e
to
c313f2f
Compare
renovate
bot
changed the title
fix(deps): update non-minor dependencies
chore(deps): update non-minor dependencies
Oct 23, 2024
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
8 times, most recently
from
October 30, 2024 22:37
fe6a807
to
dc9c42b
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
5 times, most recently
from
November 7, 2024 09:55
fa45f16
to
d1476e9
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
4 times, most recently
from
November 11, 2024 12:10
9c65b8c
to
7889b67
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
6 times, most recently
from
November 21, 2024 09:21
2b13e6d
to
d43bba8
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
5 times, most recently
from
December 9, 2024 17:49
3797a8a
to
b37ce69
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
3 times, most recently
from
December 10, 2024 11:28
dcf4bb4
to
01f07e9
Compare
renovate
bot
changed the title
chore(deps): update non-minor dependencies
fix(deps): update non-minor dependencies
Dec 10, 2024
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
6 times, most recently
from
December 17, 2024 21:04
ac318de
to
2cf85c7
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
3 times, most recently
from
December 20, 2024 02:29
75772ee
to
58f4b86
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
5 times, most recently
from
January 6, 2025 21:01
4ab0208
to
eaea9a7
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
5 times, most recently
from
January 9, 2025 15:49
d7c112d
to
fba09e5
Compare
renovate
bot
force-pushed
the
renovate/non-minor-deps
branch
from
January 10, 2025 14:23
fba09e5
to
3308c7c
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:
12-debian-12-r31
->12-debian-12-r35
v2.22.0
->v2.22.2
v1.36.0
->v1.36.2
v0.1.44
->v0.1.54
v0.3.45
->v0.3.63
v0.2.20
->v0.2.23
1.23.2
->1.23.4
v0.19.3
->v0.19.4
a9b7c2d
->d19d76c
Release Notes
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.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.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.23
Compare Source
v0.2.22
Compare Source
v0.2.21
Compare Source
golang/go (go)
v1.23.4
v1.23.3
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)
v0.19.4
Compare Source
What's Changed
Full Changelog: kubernetes-sigs/controller-runtime@v0.19.3...v0.19.4
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.