[Upd4ting]

Why

Antony's goal is a joint release from campaign/integration that publishes the planned version of every package. The planned version of @antelopejs/interface-database is 0.3.0. The manifest already holds 0.3.0, so without this change the workflow would increment from it and publish 0.4.0.

The repo's release workflow calls AntelopeJS/.github/.github/workflows/release-npm-public.yml@v1 with no release-version input. On the latest channel that workflow reads the manifest version and, only when it has a prerelease suffix, passes --increment=${version%%-*} to release-it ("Promoting a prerelease ships its base version (1.9.0-next.4 -> 1.9.0)"). A manifest of 0.3.0-rc.0 therefore makes the workflow publish 0.3.0. This is the route in release-plan.md, "Name the exact version", and the 2026-11-03 plan update, edit 3.

What changed

• package.json version: 0.3.0 -> 0.3.0-rc.0.

Proofs

• pnpm run checks at this head: Checks: 8 passed, 0 failed.
• The workflow behaviour above comes from reading release.yml and release-npm-public.yml at v1. No release, publish or dry-run script was run (Antony's approval 2/6), so the printed number is inferred from the workflow code, not measured.
• The changelog base on the default branch after landing is the newest stable tag, v0.2.0 (the workflow passes --plugins.release-it-changelogen.from= the newest v* tag without a prerelease suffix).

Attention

• Land this only after the repo's merge-main PR (done) and before the release dispatch. After the release, the release commit sets the manifest to 0.3.0.
• The merge-main PR landed as 178776a, a commit with one parent, so main's own commits are not ancestors of campaign/integration: git rev-list --count origin/campaign/integration..origin/main prints 2. Step 0's "0 behind" check still fails here, and main's release tags are not reachable from this branch. This PR does not change that.