Skip to content

Conversation

@syself-bot
Copy link
Contributor

@syself-bot syself-bot bot commented Oct 20, 2025

This PR contains the following updates:

Package Type Update Change
sigstore/cosign-installer action major v3.8.1 -> v4.0.0

Release Notes

sigstore/cosign-installer (sigstore/cosign-installer)

v4.0.0

Compare Source

What's Changed?

Note: You must upgrade to cosign-installer v4 if you want to install Cosign v3+. You may still install Cosign v2.x with cosign-installer v4.

In version v3+, using cosign sign-blob requires adding the --bundle flag which may require you to update your signing command.

  • Add support for Cosign v3 releases (#​201)

v3.10.1

Compare Source

What's Changed?

Note: cosign-installer v3.x cannot be used to install Cosign v3.x. You must upgrade to cosign-installer v4 in order to use Cosign v3.

Note: This is planned to be the final release of Cosign v2, though we will cut new releases for any critical security or bug fixes. We recommend transitioning to Cosign v3.

  • Bump default Cosign to v2.6.1 (#​203)

v3.10.0

Compare Source

What's Changed

Full Changelog: sigstore/cosign-installer@v3.9.2...v3.10.0

v3.9.2

Compare Source

What's Changed

Full Changelog: sigstore/cosign-installer@v3.9.1...v3.9.2

v3.9.1

Compare Source

What's Changed

Full Changelog: sigstore/cosign-installer@v3.9.0...v3.9.1

v3.9.0

Compare Source

What's Changed

Full Changelog: sigstore/cosign-installer@v3...v3.9.0

v3.8.2

Compare Source

What's Changed

Full Changelog: sigstore/cosign-installer@v3...v3.8.2


Configuration

📅 Schedule: Branch creation - "on monday" 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.


  • If you want to rebase/retry this PR, check this box

guettli and others added 24 commits July 31, 2025 20:29
> 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 <thomas.guettler@syself.com>
* 🌱 Deprecate (ssh) PortAfterCloudInit.

Since [PR Install Cloud-Init-Data via post-install.sh #1407](#1407) this field is not functional.

The additional reboot after InstallImage was removed.

The ssh port after InstallImage is the port which gets used.
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 <dhairya.arora@syself.com>
Remove unused method ClientConfigWithAPIEndpoint #1687
> [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.
| datasource  | package                   | from   | to     |
| ----------- | ------------------------- | ------ | ------ |
| github-tags | sigstore/cosign-installer | v3.8.1 | v4.0.0 |
@github-actions github-actions bot added size/XS Denotes a PR that changes 0-20 lines, ignoring generated files. area/github Changes made in the github directory labels Oct 20, 2025
@syself-bot
Copy link
Contributor Author

syself-bot bot commented Dec 5, 2025

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/github Changes made in the github directory size/XS Denotes a PR that changes 0-20 lines, ignoring generated files. type/major update/github-action

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants