[PR #1003] [MERGED] fix(release): publish from explicit source checkpoints #2572

Closed
opened 2026-10-17 21:07:45 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1003
Author: @N0zoM1z0
Created: 10/7/2026
Status: ✅ Merged
Merged: 10/7/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/release-checkpoint-flow


📝 Commits (3)

  • f680416 fix(release): publish from explicit source checkpoints
  • 873071f fix(release): drive checkpoint releases from frozen branches
  • 2de06e3 Merge remote-tracking branch 'origin/main' into fix/release-checkpoint-flow

📊 Changes

6 files changed (+393 additions, -33 deletions)

View changed files

📝 .github/workflows/ci.yml (+1 -1)
📝 .github/workflows/release.yml (+40 -2)
📝 CONTRIBUTING.md (+11 -29)
📝 docs/.vitepress/config.ts (+1 -0)
➕ docs/releasing.md (+103 -0)
📝 tests/boundary/filesystem/releaseWorkflow.test.ts (+237 -1)

📄 Description

Summary

Freeze release sources on release/VERSION branches so main can keep accepting changes without refreshing the release candidate.

  • Cutting/pushing the release branch prepares the Release Please PR; merging its reviewed, tested head into that branch triggers publication.
  • Remove the rolling main trigger and phase/input orchestration. Optional manual retries select the release branch with --ref.
  • Reject main/tag/invalid refs and a moved branch before Release Please creates release objects; block registry publication if the tagged SHA differs from the workflow's provenance SHA.
  • Both npm and MCP Registry check out the exact release SHA; preserve packaged-artifact verification and the published CLI/MCP/update canary.
  • Enable CI for PRs targeting release branches. Document selection, review, publication, synchronization back to main, and partial-publication recovery in the contribution guide and VitePress navigation.

Verification

  • npm run test:focused -- tests/boundary/filesystem/releaseWorkflow.test.ts tests/conformance/releaseConfiguration.test.ts — 25 tests passed (actual shell guard cases plus workflow/configuration contracts).
  • npm run check:fast — passed.
  • npm run docs:build — passed.
  • git diff --check — passed.
  • The earlier CI failures were missing build-generated source catalogs; main already fixed this in #1002, now included by updating this PR branch.

Static and fake-launcher tests do not prove registry publication; the first frozen release will separately verify the actual GitHub tag, npm consumer, and MCP Registry version. No provider behavior changes; real Hopper/Ghidra verification was not performed.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1003 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/7/2026 **Status:** ✅ Merged **Merged:** 10/7/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/release-checkpoint-flow` --- ### 📝 Commits (3) - [`f680416`](https://github.com/morluto/rea/commit/f6804166b1a3eb98198621689cf94c90ecf282c3) fix(release): publish from explicit source checkpoints - [`873071f`](https://github.com/morluto/rea/commit/873071f4e02211dff1fec7d9e52571a8d90bb29b) fix(release): drive checkpoint releases from frozen branches - [`2de06e3`](https://github.com/morluto/rea/commit/2de06e328960e6a0617fa9d987a2bc41b0f3290d) Merge remote-tracking branch 'origin/main' into fix/release-checkpoint-flow ### 📊 Changes **6 files changed** (+393 additions, -33 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+1 -1) 📝 `.github/workflows/release.yml` (+40 -2) 📝 `CONTRIBUTING.md` (+11 -29) 📝 `docs/.vitepress/config.ts` (+1 -0) ➕ `docs/releasing.md` (+103 -0) 📝 `tests/boundary/filesystem/releaseWorkflow.test.ts` (+237 -1) </details> ### 📄 Description ## Summary Freeze release sources on `release/VERSION` branches so main can keep accepting changes without refreshing the release candidate. - Cutting/pushing the release branch prepares the Release Please PR; merging its reviewed, tested head into that branch triggers publication. - Remove the rolling main trigger and phase/input orchestration. Optional manual retries select the release branch with `--ref`. - Reject main/tag/invalid refs and a moved branch **before** Release Please creates release objects; block registry publication if the tagged SHA differs from the workflow's provenance SHA. - Both npm and MCP Registry check out the exact release SHA; preserve packaged-artifact verification and the published CLI/MCP/update canary. - Enable CI for PRs targeting release branches. Document selection, review, publication, synchronization back to main, and partial-publication recovery in the contribution guide and VitePress navigation. ## Verification - `npm run test:focused -- tests/boundary/filesystem/releaseWorkflow.test.ts tests/conformance/releaseConfiguration.test.ts` — 25 tests passed (actual shell guard cases plus workflow/configuration contracts). - `npm run check:fast` — passed. - `npm run docs:build` — passed. - `git diff --check` — passed. - The earlier CI failures were missing build-generated source catalogs; main already fixed this in #1002, now included by updating this PR branch. Static and fake-launcher tests do not prove registry publication; the first frozen release will separately verify the actual GitHub tag, npm consumer, and MCP Registry version. No provider behavior changes; real Hopper/Ghidra verification was not performed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-17 21:07:45 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#2572
No description provided.