Repository navigation
fix(deps): build on go1.26.10 and sign with cosign v3.1.4 - #5543
Merged
Merged
Conversation
GO-2026-6809 (crypto/x509 trusting compromised intermediates) affects stdlib 1.26.9 and failed the release scan of v4.4.0-rc1. Every shipped binary is built from the go directive, so bump it in both modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
Patch release built with Go 1.27.3. None of its behaviour changes touch the single-artifact sign and sign-blob calls used here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
mauromorales
approved these changes
Oct 21, 2026
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
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.
Part of #5351
Summary
The
v4.4.0-rc1release run failed atscan shipped bundle(run) on one advisory, GO-2026-6809 (crypto/x509 trusts compromised intermediate certificates), instdlib@1.26.9. It was published on 2026-10-21 at 00:27 UTC, a few hours before the tag, and hits every binary we build:kairos,kairos-installerandprovider-kairos, FIPS variants included. It is fixed in Go 1.26.10.This bumps the
godirective to1.26.10ingo.modandtests/go.mod. The build, unit test and release scan jobs all take their Go version fromgo-version-file: go.mod.It also takes the open Renovate bump of cosign to v3.1.4 (#5540), a patch release built with Go 1.27.3. Of its behaviour changes, the relevant one restricts bundle signing to one artifact per call; every
cosign signandcosign sign-blobhere already signs a single artifact. Nothing here uses--use-signing-configor attached signature files.Not included
#5539 (tpm-helpers to
2cc4ae1) does not build, by design: tpm-helpers now requires a nonce inGeneratePCRQuoteandVerifyPCRQuote, which is the library half of #4828. The kcrypt wiring (three call sites) and the version skew it introduces between old nodes and a new challenger need their own change.Verification
On Go 1.26.10:
make testpasses,go vet ./...is clean intests/, andgo mod tidy -diffreports nothing in either module.govulncheck -mode binaryon a freshly builtkairos-agentno longer reports GO-2026-6809. The only remaining finding is GO-2026-5298, already ignored inosv-scanner.tomluntil 2026-11-10.The cosign bump is only exercised by release and factory runs with signing enabled, so it is not covered by the checks on this pull request.
AI disclosure
Investigation, changes and this description were produced with Claude Code. A maintainer pushed the branch; the diff is four one-line version changes.
Closes #5540
π€ Generated with Claude Code