chore(release): prepare Registry Stack v0.12.0 beta-14#419
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 090ca399f2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| release: beta-14 | ||
| version: 0.12.0 | ||
| source_repo: registrystack/registry-stack | ||
| source_ref: 865921f0d8e874e3cefe548d000e8915c4abecbc |
There was a problem hiding this comment.
When building or verifying the v0.12.0 docset, validate-docsets makes every non-external product ref match this manifest source_ref, and docs/site/scripts/fetch-openapi.mjs reads archived specs with git show <ref>:<path>. This hash is the parent of the release-prep commit, where the Relay and Notary OpenAPI files still report 0.11.0, so the v0.12.0 archived API/reference evidence would be generated from the previous release rather than the tag target containing the 0.12.0 version bumps. Point this at the actual v0.12.0 release commit and update the matching docset refs.
Useful? React with 👍 / 👎.
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c8e071db1f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| oasdiff breaking --fail-on ERR --err-ignore "$BREAKING_IGNORE" \ | ||
| --warn-ignore "$BREAKING_IGNORE" \ | ||
| "$BASELINE" "$GENERATED" | ||
| oasdiff breaking --fail-on ERR "$BASELINE" "$GENERATED" |
There was a problem hiding this comment.
When the Notary contract job runs in root CI, it sets OPENAPI_CONTRACT_BASE_REF to the PR base or push before SHA (.github/workflows/ci.yml lines 405-409); against beta-13/v0.11, that base still contains /oid4vci/credential-offer and /oid4vci/nonce, while the current spec removes them. Oasdiff documents that breaking --fail-on ERR exits 1 for ERR-level changes, and the deleted allowlist was matching these exact path-removal ERRs, so this unignored invocation will block the release PR/first main push even though the removals are the intentional 0.12 migration.
Useful? React with 👍 / 👎.
1 participant
Summary
Prepare Registry Stack beta-14 / v0.12.0 from the frozen
release/1.0integration head.Scope boundary
This PR contains one release-preparation commit on exact integration source
865921f0d8e874e3cefe548d000e8915c4abecbc. It preserves the already integrated scope and does not add draft PR #418, Dependabot updates targetingmain, or any new ticket work.This beta is pre-1.0. It does not claim stable 1.0 readiness, hosted publication, Solmara repin, external wallet conformance, upgrade/rollback evidence, or independent pilot evidence.
Verification
Passed locally:
Residual non-blocking evidence notes:
spin 0.9.8warning without an advisorySigned-off-by: Jeremi Joslin jeremi@joslin.fr