Problem
package.json currently declares "version": "0.5.0", but the only published git tag is v1.0.0. The two are out of sync, which makes it ambiguous which version is actually "released."
Goal
Pick a single source of truth (recommend git tags + commit-and-tag-version automation, matching Nerva) and bring package.json into alignment.
Acceptance criteria
Context
Found during a cross-repo versioning audit. Claudius has the same issue and is tracked separately.
Problem
package.jsoncurrently declares"version": "0.5.0", but the only published git tag isv1.0.0. The two are out of sync, which makes it ambiguous which version is actually "released."Goal
Pick a single source of truth (recommend git tags +
commit-and-tag-versionautomation, matching Nerva) and bringpackage.jsoninto alignment.Acceptance criteria
package.jsonversion matches the latest published tagpnpm run releasekeep both in sync automaticallyContext
Found during a cross-repo versioning audit. Claudius has the same issue and is tracked separately.