chore: Bump actions and pre-commit hook refs#84
Conversation
Techassi
commented
Oct 24, 2025
- Bump actions
- Bump actions/checkout to v5.0.0
- Bump sigstore/cosign-installer to v4.0.0
- Bump anchore/sbom-action to v0.20.9
- Bump docker/login-action to v3.6.0
- Bump cachix/install-nix-action to v31.8.1
- Bump actions/setup-python to v6.0.0
- Bump actions/cache to v4.3.0
- Bump Swatinem/rust-cache to v2.8.1
- Bump actions/download-artifact to v5.0.0
- Bump actions/upload-artifact to v4.6.2
- Bump slackapi/slack-github-action to v2.1.1
- Bump softprops/action-gh-release to v2.4.1
- Bump pre-commit hook refs
- Bump pre-commit/pre-commit-hooks to 6.0.0
- Bump adrienverge/yamllint to 1.37.1
- Bump igorshubovych/markdownlint-cli to 0.45.0
- Bump koalaman/shellcheck-precommit to 0.11.
- Bump rhysd/actionlint to 1.7.8
- Bump sigstore/cosign-installer to v4.0.0 - Bump anchore/sbom-action to v0.20.9 - Bump docker/login-action to v3.6.0 - Bump cachix/install-nix-action to v31.8.1 - Bump actions/setup-python to v6.0.0 - Bump actions/cache to v4.3.0 - Bump Swatinem/rust-cache to v2.8.1 - Bump actions/download-artifact to v4.6.2 - Bump slackapi/slack-github-action to v2.1.1
- Bump pre-commit/pre-commit-hooks to 6.0.0 - Bump adrienverge/yamllint to 1.37.1 - Bump igorshubovych/markdownlint-cli to 0.45.0 - Bump koalaman/shellcheck-precommit to 0.11. - Bump rhysd/actionlint to 1.7.8
- Bump actions/checkout to v5.0.0 - Bump actions/upload-artifact to v4.6.2 - Bump actions/download-artifact to v5.0.0 - Bump softprops/action-gh-release to v2.4.1
NickLarsenNZ
left a comment
There was a problem hiding this comment.
Approved on the condition that changes/changelogs were checked before bumping to the latest.
|
The changelogs were checked by me and no commit immediately stood out as malicious. I also didn't spot any breaking change which requires changes on our side. |
Release NoteBREAKING: With the release of SDP 25.11, we now sign container images and Helm charts using cosign 3 and its new bundle format, benefiting from the OCI Referrers API. This means to verify signatures of this and future releases, customers need to use cosign 3. Verification using cosign 2 is also possible if you're using version 2.6.0 or above and provide the additional flag |