Skip to content

armgit / rea

Public Imported from GitHub
0

Reverse engineer anything with agents, from app behavior down to native binaries.

fix(release): sync 5.0.0 checkpoint back to main

morluto966cca8efe5e
diff --cc docs/releasing.md
index 5e8c977c5,fe453323c..2a28ee39a
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@@ -89,19 -78,16 +89,35 @@@ Record these outcomes separately
A GitHub tag alone does not establish npm or MCP Registry publication.
-## Sync metadata back to main
+## 4. Sync metadata back to main
+
++Post-release synchronization is part of completing the release. Finish it
++before cutting the next checkpoint; otherwise main retains the previous
++release baseline and can propose an already-published version again.
+
After publication, open a PR from the release branch back to main. Preserve
main's later implementation changes and resolve generated-file conflicts by
regenerating from the combined contracts with the released package version.
Review and test this synchronization PR, then use a merge commit so the release
tag remains in main's ancestry. Keep the released tag unchanged.
++The synchronization must include `.release-please-manifest.json`,
++`package.json`, both root versions in `package-lock.json`, `CHANGELOG.md`,
++`server.json`, and the versioned documentation examples. Run
++`npm run docs:generate`, `npm run docs:check`, and the release configuration
++tests against the combined tree. After the merge, verify that the released
++tag is an ancestor of main:
++
++```bash
++git fetch origin main --tags
++git merge-base --is-ancestor rea-agents-5.0.0 origin/main
++```
++
Close any superseded rolling release PR. Future releases repeat the checkpoint
procedure from main; never resume automatic release-PR refreshes on main pushes.
+The generated-metadata workflow stays limited to pull requests into main so it
+does not push commits onto a frozen candidate. Preparation normalizes
+`docs/product-catalog.json` on the bot pull request.
## Partial publication and retries
diff --cc tests/conformance/releaseConfiguration.test.ts
index 6988de6f9,6988de6f9..28dbbabfb
--- a/tests/conformance/releaseConfiguration.test.ts
+++ b/tests/conformance/releaseConfiguration.test.ts
@@@ -63,15 -63,15 +63,33 @@@ describe("release configuration", () =
"marks the versioned package example in %s",
async (path) => {
const content = await readFile(path, "utf8");
++ const packageJson = (await readJson("package.json")) as {
++ version: string;
++ };
const versionBlock =
/<!-- x-release-please-start-version -->[\s\S]*?<!-- x-release-please-end -->/u.exec(
content,
)?.[0];
-- expect(versionBlock).toMatch(/rea-agents@\d+\.\d+\.\d+/u);
++ expect(versionBlock).toContain(`rea-agents@${packageJson.version}`);
},
);
++ it("keeps the release baseline, lockfile, and changelog aligned with the package version", async () => {
++ const packageJson = (await readJson("package.json")) as {
++ version: string;
++ };
++ expect(await readJson(".release-please-manifest.json")).toEqual({
++ ".": packageJson.version,
++ });
++ expect(await readJson("package-lock.json")).toMatchObject({
++ version: packageJson.version,
++ packages: { "": { version: packageJson.version } },
++ });
++ const changelog = await readFile("CHANGELOG.md", "utf8");
++ expect(/^## \[([^\]]+)\]/mu.exec(changelog)?.[1]).toBe(packageJson.version);
++ });
++
it("keeps the npm package and MCP Registry metadata aligned", async () => {
const packageJson = (await readJson("package.json")) as {
name: string;