[PR #1340] [MERGED] chore(release): sync 6.2.0 checkpoint into main #2808

New issue

Closed

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

bsakaguchi commented

2026-10-17 21:10:30 +00:00

Owner

📋 Pull Request Information

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

Base: main ← Head: chore/sync-release-6.2.0

📝 Commits (2)

a64851f chore(release/6.2.0): release rea-agents 6.2.0 (#1305)
0c3aa98 chore(release): sync 6.2.0 checkpoint into main

📊 Changes

8 files changed (+259 additions, -9 deletions)

View changed files

📝 .release-please-manifest.json (+1 -1)
📝 CHANGELOG.md (+243 -0)
📝 docs/installation.md (+1 -1)
📝 docs/migration-6.2.md (+7 -0)
📝 package-lock.json (+2 -2)
📝 package.json (+2 -2)
📝 server.json (+2 -2)
📝 src/generatedPackageMetadata.ts (+1 -1)

📄 Description

Sync the published 6.2.0 checkpoint into main while preserving main's later implementation changes. The integration merge retains rea-agents-6.2.0 (a64851f2592cd353600d54864b38524705341dd1) in its ancestry.

Only eight release metadata/documentation files change: version authorities, the 6.2 changelog and migration notes, the pinned installation example, and the reviewed CHANGELOG-only formatter hook fix. Regenerated catalogs, conformance projections and packaged skills remain ignored outputs.

GitHub release and npm latest now identify 6.2.0. The public npm package's gitHead matches the frozen SHA; an isolated public-package canary passes CLI/MCP inventory (139 tools) and the 6.1.0 to 6.2.0 update path. The original publication workflow has completed successfully, including the public npm canary and MCP Registry publication. The public Registry record is active/latest at version 6.2.0 and references rea-agents@6.2.0. Merge after this PR's final CI passes. Publication run: https://github.com/morluto/rea/actions/runs/37961536716

Validation:

npm run docs:generate, npm run docs:check, and npm run build:cached pass.
npm run test:focused -- tests/conformance/releaseConfiguration.test.ts tests/boundary/filesystem/releaseWorkflow.test.ts tests/boundary/filesystem/releaseCheckpoint.test.ts — 75 tests pass.
Pre-commit formatting/lint and pre-push npm run check:fast pass; git diff --check passes.
The integration tree matches the conflict-free three-way merge preview and preserves main's implementation files.

Use a merge commit, preserving the release tag's ancestry. Close superseded main release proposal #1154 immediately before merging, then verify tag ancestry and the next proposal's release baseline. The 40k celebration #1334 is a separate number-only documentation PR, now ready for review after reaching the milestone.

The frozen released tree has real Linux x64 Ghidra verification; no new real Hopper/Ghidra verification was performed for this metadata synchronization.

_{🔄 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/1340 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/9/2026 **Status:** ✅ Merged **Merged:** 10/9/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `chore/sync-release-6.2.0` --- ### 📝 Commits (2) - [`a64851f`](https://github.com/morluto/rea/commit/a64851f2592cd353600d54864b38524705341dd1) chore(release/6.2.0): release rea-agents 6.2.0 (#1305) - [`0c3aa98`](https://github.com/morluto/rea/commit/0c3aa98a3edba1c80d0325ba219c9fbc0767514e) chore(release): sync 6.2.0 checkpoint into main ### 📊 Changes **8 files changed** (+259 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `.release-please-manifest.json` (+1 -1) 📝 `CHANGELOG.md` (+243 -0) 📝 `docs/installation.md` (+1 -1) 📝 `docs/migration-6.2.md` (+7 -0) 📝 `package-lock.json` (+2 -2) 📝 `package.json` (+2 -2) 📝 `server.json` (+2 -2) 📝 `src/generatedPackageMetadata.ts` (+1 -1) </details> ### 📄 Description Sync the published 6.2.0 checkpoint into main while preserving main's later implementation changes. The integration merge retains `rea-agents-6.2.0` (`a64851f2592cd353600d54864b38524705341dd1`) in its ancestry. Only eight release metadata/documentation files change: version authorities, the 6.2 changelog and migration notes, the pinned installation example, and the reviewed CHANGELOG-only formatter hook fix. Regenerated catalogs, conformance projections and packaged skills remain ignored outputs. GitHub release and npm `latest` now identify 6.2.0. The public npm package's `gitHead` matches the frozen SHA; an isolated public-package canary passes CLI/MCP inventory (139 tools) and the 6.1.0 to 6.2.0 update path. The original publication workflow has completed successfully, including the public npm canary and MCP Registry publication. The public Registry record is active/latest at version 6.2.0 and references `rea-agents@6.2.0`. Merge after this PR's final CI passes. Publication run: https://github.com/morluto/rea/actions/runs/37961536716 Validation: - `npm run docs:generate`, `npm run docs:check`, and `npm run build:cached` pass. - `npm run test:focused -- tests/conformance/releaseConfiguration.test.ts tests/boundary/filesystem/releaseWorkflow.test.ts tests/boundary/filesystem/releaseCheckpoint.test.ts` — 75 tests pass. - Pre-commit formatting/lint and pre-push `npm run check:fast` pass; `git diff --check` passes. - The integration tree matches the conflict-free three-way merge preview and preserves main's implementation files. Use a **merge commit**, preserving the release tag's ancestry. Close superseded main release proposal #1154 immediately before merging, then verify tag ancestry and the next proposal's release baseline. The 40k celebration #1334 is a separate number-only documentation PR, now ready for review after reaching the milestone. The frozen released tree has real Linux x64 Ghidra verification; no new real Hopper/Ghidra verification was performed for this metadata synchronization. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-17 21:10:30 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-10-31 01:06:25 +00:00

[PR #2808] [MERGED] fix(cli): refuse a JavaScript integrity policy the binary analyze lane cannot honor #5410

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

No description provided.

Rows
Columns