🌱 Update Golang Dependencies group to v0.45.0 [SECURITY] #1720
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
🌱 Remove unused function.
> I0829 08:31:00.251753 17515 request.go:697] > Waited for 1.993332996s due to client-side > throttling, not priority and fairness, request: > GET:https://127.0.0.1:39499/apis/cluster.x-k8s.io/v1beta1/machines This warnings is repeated again and again in the output of e2e tests. We use current api-servers, no need for client-side throttling.
🌱 Use errors.Join(reterr, err) to handle both errors.
Update metadata.yaml Add kind property Co-authored-by: Thomas Güttler <[email protected]>
Update output-for-watch.sh and tail-controller-logs.sh: support caph running in a different namespace (not fix to capi-system). update-operator-dev-deployment.sh: Be sure to not update the cluster, if connected via oidc (avoid accidentally changing a non-test system)
* 🌱 avoid unhealthy conditions when cluster starts. Closes #1674
Co-authored-by: Dhairya Arora <[email protected]>
> [It] should take over an existing load balancer with correct name
* 🌱 HCloudMachineType: allow all values. The list of valid machine types gets changed by Hetzner from time to time. CAPH no longer validates this string. It is up to you to use a valid type. Not all types are available in all locations. Additionally Remediation was fixed if providerID was nil.
> It("checks that no remediation is tried if HCloud server does not exist anymore
…1700) Bump clusterctl version Co-authored-by: don <[email protected]> Co-authored-by: Thomas Güttler <[email protected]>
Otherwise error messages from a second process running in the background are not visible.
| datasource | package | from | to | | ---------- | ------------------- | ------- | ------- | | go | golang.org/x/crypto | v0.40.0 | v0.45.0 |
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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:
v0.40.0->v0.45.0GitHub Vulnerability Alerts
CVE-2025-58181
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
CVE-2025-47914
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, 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.