morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[PR #1012] [MERGED] fix(release): support default credentials and record 5.0.0 boundary #2579

New issue

Closed

opened 2026-10-17 21:07:49 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-17 21:07:49 +00:00

Owner

📋 Pull Request Information

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

Base: main ← Head: fix/release-default-credentials

📝 Commits (3)

36eca26 chore(release): sync 5.0.0 metadata to main
1784ca9 fix(release): support built-in credentials and refresh release boundary
a42e579 chore: merge current main for release follow-up

📊 Changes

4 files changed (+91 additions, -49 deletions)

View changed files

📝 .github/workflows/release.yml (+4 -14)
📝 docs/installation.md (+12 -7)
📝 docs/releasing.md (+12 -8)
📝 tests/boundary/filesystem/releaseWorkflow.test.ts (+63 -20)

📄 Description

Summary

Complete the checkpoint-release documentation and default-credential path after #1006 and the maintainer's direct 5.0.0 metadata synchronization.

Only four files change:

Restore optional RELEASE_PLEASE_TOKEN with GITHUB_TOKEN fallback for Release Please and the canonical catalog push. Current GitHub creates approval-required PR workflows for bot-authored opened/synchronize/reopened events; maintainers approve the final normalized head.
Remove the hard failure that prevents this repository's next prepare/publish when a separate secret is absent.
Preserve #1006's manual prepare/publish phases, frozen branch selection, pre-tag source check and exact-SHA/provenance publication guards.
Correct the installation guide's checked-release boundary to 5.0.0, 133 tools, 2026-10-07, and the actual checkpoint/public consumer verification.

Related: #1006, #1007, #1010. #1010 was closed after the maintainer synced metadata directly; this follow-up contains its remaining corrections only. Main already includes the public release tag ancestry and version 5.0.0. The published artifact and tag remain at b33236ec08.

Evidence

GitHub's current trigger documentation explicitly supports GITHUB_TOKEN-authored PR runs in an approval-required state. This was verified in #1007: five exact-head runs were approved, all 26 checks passed, and the official release run published GitHub/npm/MCP 5.0.0. The public consumer verified CLI, 133/133 MCP tools, target-free session and an isolated 4.1.0 -> 5.0.0 update. Registry gitHead/provenance and artifact digest match the frozen checkpoint.

Regression before the fix: three new test failures against the mandatory-token workflow. After fixing token selection and the pre-action guard, both prepare/publish succeed with or without a custom credential in the actual workflow shell preflight.

Verification

npm run build:cached — passed after merging latest main.
npm run test:focused -- tests/boundary/filesystem/releaseWorkflow.test.ts tests/conformance/releaseConfiguration.test.ts — 36 passed (latest main adds one release-baseline test).
npm run check:fast — passed.
npm run docs:check — passed.
npm run docs:build — passed for changed guide content.
git diff --check — passed.

No CLI/MCP or provider behavior changes. Real Hopper/Ghidra verification was not performed; the actual default-token release path and public package were verified as linked above. CI runs on this final follow-up head before merge.

_{🔄 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/1012 **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-default-credentials` --- ### 📝 Commits (3) - [`36eca26`](https://github.com/morluto/rea/commit/36eca26b38d11edb1df498f1caa7139f09d04c5c) chore(release): sync 5.0.0 metadata to main - [`1784ca9`](https://github.com/morluto/rea/commit/1784ca940ae7803bab9c580ff049cd1db88c311c) fix(release): support built-in credentials and refresh release boundary - [`a42e579`](https://github.com/morluto/rea/commit/a42e5795be758d1e812a5ee536dc7bd02f689e31) chore: merge current main for release follow-up ### 📊 Changes **4 files changed** (+91 additions, -49 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+4 -14) 📝 `docs/installation.md` (+12 -7) 📝 `docs/releasing.md` (+12 -8) 📝 `tests/boundary/filesystem/releaseWorkflow.test.ts` (+63 -20) </details> ### 📄 Description ## Summary Complete the checkpoint-release documentation and default-credential path after #1006 and the maintainer's direct 5.0.0 metadata synchronization. Only four files change: - Restore optional `RELEASE_PLEASE_TOKEN` with `GITHUB_TOKEN` fallback for Release Please and the canonical catalog push. Current GitHub creates approval-required PR workflows for bot-authored opened/synchronize/reopened events; maintainers approve the final normalized head. - Remove the hard failure that prevents this repository's next prepare/publish when a separate secret is absent. - Preserve #1006's manual prepare/publish phases, frozen branch selection, pre-tag source check and exact-SHA/provenance publication guards. - Correct the installation guide's checked-release boundary to 5.0.0, 133 tools, 2026-10-07, and the actual checkpoint/public consumer verification. Related: #1006, #1007, #1010. #1010 was closed after the maintainer synced metadata directly; this follow-up contains its remaining corrections only. Main already includes the public release tag ancestry and version 5.0.0. The published artifact and tag remain at b33236ec082ae3a59421232f9067c095283c3f6d. ## Evidence [GitHub's current trigger documentation](https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow) explicitly supports GITHUB_TOKEN-authored PR runs in an approval-required state. This was verified in #1007: five exact-head runs were approved, all 26 checks passed, and the [official release run](https://github.com/morluto/rea/actions/runs/37659102164) published GitHub/npm/MCP 5.0.0. The public consumer verified CLI, 133/133 MCP tools, target-free session and an isolated 4.1.0 -> 5.0.0 update. Registry gitHead/provenance and artifact digest match the frozen checkpoint. Regression before the fix: three new test failures against the mandatory-token workflow. After fixing token selection and the pre-action guard, both prepare/publish succeed with or without a custom credential in the actual workflow shell preflight. ## Verification - `npm run build:cached` — passed after merging latest main. - `npm run test:focused -- tests/boundary/filesystem/releaseWorkflow.test.ts tests/conformance/releaseConfiguration.test.ts` — 36 passed (latest main adds one release-baseline test). - `npm run check:fast` — passed. - `npm run docs:check` — passed. - `npm run docs:build` — passed for changed guide content. - `git diff --check` — passed. No CLI/MCP or provider behavior changes. Real Hopper/Ghidra verification was not performed; the actual default-token release path and public package were verified as linked above. CI runs on this final follow-up head before merge. --- <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:49 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-10-31 01:07:54 +00:00

[PR #3084] [CLOSED] fix(overview)!: report uninterpretable segment lengths as unknown #5601

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#2579

No description provided.

Rows
Columns