Repository navigation
fix(release): every PrismPM version site follows the workspace version - #676
Merged
Merged
Conversation
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
Member
Author
|
The Generated by Claude Code |
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.
The v0.5.0 rehearsal on main (run 43599847911) failed in its policy job.
scripts/release-gate-evidence.mjsonly admittedprismpm-0.4.0-*.tar.gzas 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-evidence.mjsand its test name the archive by the workspace version.library-sdk-check,library-sdk-check-shell,sdk-construction-handoff,sdk-construction-recordandunpublished-sdk-registryread the workspace version fromCargo.toml. They read it lazily, because some tests run copied into a sandbox.SDK_VERSIONdefault, 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.These tests pass locally:
release-native-contract,release-gate-evidence, factory,lexlean-pin,library-sdk-check(including the shell test, run without the symlinkednode_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_TOKENbecauseRELEASE_PLEASE_TOKENis not set, so no CI ran on the bot's final version of #661.Generated by Claude Code