release-check

Release check

Walk this checklist before pushing a v* tag. Report each item as pass/fail with the evidence you observed. Do NOT push anything — this command only verifies.

Checklist

1. Establish the TRUE latest release before anything else — MANDATORY FIRST STEP. Never take the current version from AGENTS.md, a plan doc, or the prompt. Probe all four:

   npm view @chanmeng666/archlang version      # what is actually on the registry
   git tag --sort=-v:refname | head            # what is actually tagged
   gh release list --limit 3                   # what actually has a Release
   grep -m3 '^## ' CHANGELOG.md                # the top heading(s)
   

   Then require both:

   • the target version is strictly greater than every one of those (an npm version is immutable — a target that already exists cannot be published, only skipped); and
   • its semver class matches what actually changed — read git log <lasttag>..main and git diff --stat <lasttag>..main, not the plan's number. New grammar/keyword, new E_*/W_* code, new public field ⇒ MINOR at least.

   If AGENTS.md disagrees with the probe, AGENTS.md is wrong — fix it (item 5) and carry on. (2026-07-25: AGENTS.md sat stale at v1.17.0 while v1.18.0 was already published, so an approved plan targeted 1.18.0; the batch actually shipped as 1.19.0.)

2. Versions consistent where they must be.

   • Root package.json version matches the latest entry heading in CHANGELOG.md.
   • Ask whether the shim changed — don't assume: git diff <lasttag>..main -- packages/mcp. ANY mcp-visible change forces the double version bump, including prose: a tool description, the README (it is the npm package page), or a server.json field like websiteUrl. The bump must land in both packages/mcp/package.json and packages/mcp/server.json (both of its version fields) — release.yml npm view-skips a version already on the registry, so an unbumped edit silently never reaches npm or the MCP registry.
   • The shim's core dependency range (^1.x) still satisfies the new core version. (The shim need NOT bump when only the core changes, the diff above is empty, and its dep range already covers the new version — e.g. core 1.15.0 with the shim at 0.2.0 depending on ^1.14.0.)