Skip to content

compat: cosign by its pin, built; boot:previous fetches the release before - #115

Merged
aledbf merged 1 commit into
mainfrom
compat-cosign
Oct 13, 2026
Merged

aledbf merged 1 commit into
mainfrom
compat-cosign

Conversation

@aledbf

@aledbf aledbf commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Follow-up to #114. The first compat.yml run on main stopped at sigstore/cosign-installer (exit 127): the action runs envsubst, and the KVM runner (Spin OS) has none.

  • New cosign entry in versions.yaml (v3.0.6, the version the installer action installs), run with go run.
  • New task boot:previous: fetches the newest release (or PREVIOUS=), checks its sha256 and signature, and writes the tree's path to _output/compat/previous. boot:compat and compat.yml both read it, so the fetch logic lives in one place.

Checked locally: boot:previous verifies v20261013.01 with the built cosign, and boot:compat passes. task lint green.

The runner also logged 0 MB free disk, which may stop the next run regardless.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

…previous

sigstore/cosign-installer runs envsubst, which the KVM runner does not have:
compat.yml's first run on main stopped there (exit 127). boot:previous fetches
the newest release (or PREVIOUS), checks its sha256 and its signature with
cosign built from versions.yaml's pin, and writes the tree's path to
_output/compat/previous; boot:compat and compat.yml both take it from there.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@aledbf
aledbf merged commit 4f7d55e into main Oct 13, 2026
7 checks passed
@aledbf
aledbf deleted the compat-cosign branch October 13, 2026 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant