Skip to content

🌱 ci: build stamped fork pilot binaries on tuna/v6 - #178

Merged
hanthor merged 1 commit into
tuna/v6from
ci/tuna-pilot-binary
Nov 13, 2026
Merged

hanthor merged 1 commit into
tuna/v6from
ci/tuna-pilot-binary

Conversation

@hanthor

@hanthor hanthor commented Nov 13, 2026

Copy link
Copy Markdown
Member

Fork-only CI split out of #172 (originally 206e36a + ce45704), reviewed on its own as the owner hold on #172 asked.

What it does

tuna-pilot-binary.yml builds linux/amd64 + linux/arm64 hive binaries from the exact tuna/v6 commit (push to tuna/v6, or manual dispatch), stamps version/commit into them, and uploads them with COMMIT and SHA256SUMS as a 30-day workflow artifact for the Spindle Compose pilot.

Least-privilege review

  • permissions: contents: read only; no secrets.*, no pull_request/pull_request_target trigger, so no untrusted code runs with a token.
  • persist-credentials: false on checkout; every action is pinned by full SHA (same pins already used on tuna/v6).
  • Publishes nothing: no release, tag, image or package. Artifacts expire after 30 days.
  • .github/release-lines.yml classifies it as pinned to tuna/v6 (-v4, -v5 excluded) so the release-line guard stays green.
  • Dropped vs ✨ Refresh v6 pilot and enable upstream ambient code-rain testingΒ #172: the now-obsolete deploy/upstream-v6-matrix trigger and dead pull_request refs.

Verification (local; Actions is currently blocked on this repo GitHub-side)

  • src/scripts/check-release-lines.sh β†’ PASS; src/scripts/test-release-lines-guard.sh β†’ PASS
  • uvx zizmor@1.32.0 .github/workflows/tuna-pilot-binary.yml β†’ 0 medium/high; one low self-repository help, same ./.github/actions/... convention as docker.yml, cli-pin-bump.yml, go-security-analysis.yml.
  • src/scripts/check-changelog-fragment.sh tuna/v6 β†’ no fragment needed (no src/ change).

Fork-only (tuna-os). Builds linux/amd64 and linux/arm64 hive binaries from
the exact tuna/v6 commit, stamps them with the commit and uploads them as a
30-day workflow artifact with SHA256SUMS for the Spindle Compose pilot.

Least privilege: contents: read only, no secrets, persist-credentials: false,
all actions pinned by SHA; nothing is published (no release, image, tag or
package). Classified as pinned to tuna/v6 in .github/release-lines.yml so the
release-line guard stays green.

Split out of #172 (originally 206e36a and ce45704); the obsolete
deploy/upstream-v6-matrix trigger and unused pull_request refs are dropped.

Signed-off-by: James Reilly <jreilly1821@gmail.com>
@hanthor

hanthor commented Nov 13, 2026

Copy link
Copy Markdown
Member Author

Decision (for @hanthor): merge. Fork-only CI split from #172, reviewed least-privilege: read-only token, no secrets, no PR-triggered execution, SHA-pinned actions, persist-credentials off, publishes only a 30-day workflow artifact (no release/image/tag). Release-line guard + self-test PASS, zizmor 1.32.0 has no medium/high findings, changelog check OK, all run locally because GitHub Actions is blocked on tuna-os/hive (GitHub-side, support ticket pending), so no CI can report. Reversible with a single revert.

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