Skip to content

fix(release): attest-build-provenance@v4 needs subject-path, not path - #9164

Merged
gHashTag merged 1 commit into
masterfrom
fix/t27o-release-subject-path
Oct 11, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/t27o-release-subject-path

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

The t27o release workflow's first real run (tag t27o-v0.1.0, run 38170030354) built and cosign-signed everything, then died at the attestation step:

actions/attest-build-provenance@v4
Error: One of subject-path, subject-digest, or subject-checksums must be provided

attest-build-provenance v4 takes subject-path, not path (the old name was dropped upstream). The workflow passes with: {path: "dist/*"}, so the action saw no subject and failed; the release step never ran and nothing was published.

One-word fix: path -> subject-path. .github/workflows/t27o-release.yml is already carried by tools/policy/foreign-exceptions.txt (#9160).

After this merges, the tag is re-pushed at the new master tip so the release actually publishes.

Refs #8996

🤖 Generated with Claude Code

… (Refs #8996)

First tag run (t27o-v0.1.0, run 38170030354) built and signed everything,
then the attestation step refused: 'One of subject-path, subject-digest,
or subject-checksums must be provided'. v4 dropped the old path input
name. One-word fix; the release step never ran, so nothing was published
and the tag is re-pushed after this merges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) October 11, 2026 20:11
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-11 20:12:28 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=224a06ef18b7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 7c74ebc into master Oct 11, 2026
20 of 24 checks passed
gHashTag added a commit that referenced this pull request Oct 12, 2026
…+ recipes AF4 round 2 (attest-input-rename) (#9297)

Matrix-regen fired for the first time on real drift: gates.t27 was 3 rows off
master (.github/workflows gained t27o-golden and t27o-release from #9147, and
#9117 deleted brain-seal-refresh). Regen per docs/claw/README.md: census
61 blocking + 3 soft + 2 reporting, pins re-indexed (oracle-nightly 30->29,
queen-publish 42->41, new rows pinned at 57/58 with their events).

recipes.t27 AF4 round 2 (#9285): +1 verified row -- t27o-release /
attest-input-rename (#9164: attest-build-provenance v4 renamed the input
path -> subject-path; one-word workflow edit, then delete and re-push the tag).
Table 21 -> 22 rows, census C_AUTO 16 / C_REVIEW 3 / C_OWNER 3. The fallback
row's COND now carries the compare-vs-master discipline every night tick ran
(a red on a PR describes the branch; its cause may be master; a stale failed
run describes an old SHA).

Two bound defects fixed in the same commit:
- recipes all_kinds_unique kept 19-row while bounds through the 21-row table
  (rows 19-20 were never compared); it takes the row count as a parameter now,
  tied to COUNT by the test.
- gates all_names_unique inner bound stayed 65 when the outer grew to 66: the
  computed range (i+1)..65 at i=65 inverts (66..65) and the lowering does not
  clamp it to empty -- the walk went wrong and no_duplicate_names_pairwise
  failed. Both bounds are 66 now, with a comment naming the trap; the unclamped
  inverted range is recorded for the compiler lane.

Lab (fresh t27c from master tip): typecheck OK both files; gates 10/10 tests,
recipes 11/11, 0 FAIL, 0 vacuous. ASCII clean, no new duplicate groups.

Refs #9285, #9281. Part of #9271.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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