Skip to content

fix(release): every PrismPM version site follows the workspace version - #676

Merged
afflom merged 2 commits into
mainfrom
claude/project-thread-f85vf3
Nov 14, 2026
Merged

afflom merged 2 commits into
mainfrom
claude/project-thread-f85vf3

Conversation

@afflom

@afflom afflom commented Nov 14, 2026

Copy link
Copy Markdown
Member

The v0.5.0 rehearsal on main (run 43599847911) failed in its policy job. scripts/release-gate-evidence.mjs only admitted prismpm-0.4.0-*.tar.gz as the native archive.

These fixes were also on the 0.5.0 release branch (commit 0acfcbf). The release-please bot re-ran and force-pushed that branch before #661 merged, so they were lost. This PR puts them on main, together with the policy fix:

  • Release gate: release-gate-evidence.mjs and its test name the archive by the workspace version.
  • SDK check fixtures: the image-label fixtures in library-sdk-check, library-sdk-check-shell, sdk-construction-handoff, sdk-construction-record and unpublished-sdk-registry read the workspace version from Cargo.toml. They read it lazily, because some tests run copied into a sandbox.
  • Version sites: the SDK inventory rows for prismpm, the action and the reusable workflow, the Dockerfile SDK_VERSION default, and the oracles/runtime package versions are now 0.5.0. They are also release-please extra-files, using generic markers and JSON paths, so the next bump writes them.
  • xtask: the reproducibility assembly names its archive, SBOM and manifest by the workspace version.

These tests pass locally: release-native-contract, release-gate-evidence, factory, lexlean-pin, library-sdk-check (including the shell test, run without the symlinked node_modules), sdk-construction-*, sdk-image-inputs, ci-capacity, release-publication, unpublished-sdk-qualification, release-config and changelog.

The ones that fail locally fail the same way on main: they need cosign, oras, buildx, offline cargo or a private TLS interface, which this environment doesn't have.

There is a process gap behind this. The release PR is pushed with GITHUB_TOKEN because RELEASE_PLEASE_TOKEN is not set, so no CI ran on the bot's final version of #661.


Generated by Claude Code

The image-label fixtures in the SDK check tests read the workspace version
instead of 0.4.0. The SDK inventory rows, the Dockerfile SDK_VERSION
default and the oracles/runtime package versions are 0.5.0 and are now
release-please extra-files, so the next bump writes them. xtask's
reproducibility assembly names its archive, SBOM and manifest by the
workspace version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3PocMnfsTUbhe5XHQx
The release run's policy job refused v0.5.0 because release-gate-evidence
only admitted prismpm-0.4.0-*.tar.gz. The archive name and its fixtures
now follow the workspace version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3PocMnfsTUbhe5XHQx

afflom commented Nov 14, 2026

Copy link
Copy Markdown
Member Author

The candidate failure in Release-qualify is expected here, the same as on #641 and #661. No release-line run has built and signed all 7 candidate images yet (sdk-build is new), so no candidate is an ancestor of this revision. The first full rehearsal after this merges will produce one. This PR only fixes the version sites and the release-gate-evidence archive pattern that stopped rehearsal 43599847911.


Generated by Claude Code

@afflom
afflom merged commit 88f0a2f into main Nov 14, 2026
18 of 19 checks passed
@afflom
afflom deleted the claude/project-thread-f85vf3 branch November 14, 2026 16:42
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.

2 participants