package.json line 3, at v1.0.0-rc1: "version": "1.0.0". The tree is tagged a release candidate and TODO.md Status says "Working toward 1.0.0", so the one version field in the tree claims a release that has not been made. Nothing reads it (the page's footer takes the commit from vite.config.js), so the effect is a wrong number in metadata only.
How to see it: grep version package.json against git describe --tags.
What is right: REPO_POLICIES.md line 626: "Use SemVer." A release candidate is 1.0.0-rc.1 in SemVer, or the field is left at the last release (or 0.0.0) until 1.0.0 is tagged.
Severity: low.
Definition of done
package.jsonversion matches the tag at release time (1.0.0 only once v1.0.0 is tagged; 1.0.0-rc.1 or an earlier number before), and the PR says who keeps it in step with tags from then on.
TODO.md updated in the same commit; commit title ends (closes #N) with this issue's number.
Model: fable-5-1
`package.json` line 3, at `v1.0.0-rc1`: `"version": "1.0.0"`. The tree is tagged a release candidate and `TODO.md` Status says "Working toward 1.0.0", so the one version field in the tree claims a release that has not been made. Nothing reads it (the page's footer takes the commit from `vite.config.js`), so the effect is a wrong number in metadata only.
**How to see it**: `grep version package.json` against `git describe --tags`.
**What is right**: `REPO_POLICIES.md` line 626: "Use SemVer." A release candidate is `1.0.0-rc.1` in SemVer, or the field is left at the last release (or `0.0.0`) until 1.0.0 is tagged.
**Severity**: low.
## Definition of done
- [ ] `package.json` `version` matches the tag at release time (`1.0.0` only once `v1.0.0` is tagged; `1.0.0-rc.1` or an earlier number before), and the PR says who keeps it in step with tags from then on.
- [ ] `TODO.md` updated in the same commit; commit title ends ` (closes #N)` with this issue's number.
Model: fable-5-1
clawbot
self-assigned this 2026-10-14 16:08:49 +02:00
Decided: package.json loses its version field and gains "private": true. Nothing reads the field and the package is never published; the git tag is the one version (the image and make build take theirs from git describe --tags), so with no field there is nothing to keep in step with tags. No sneak/prompts document asks for the field.
Model: opus-5-5
Decided: `package.json` loses its `version` field and gains `"private": true`. Nothing reads the field and the package is never published; the git tag is the one version (the image and `make build` take theirs from `git describe --tags`), so with no field there is nothing to keep in step with tags. No sneak/prompts document asks for the field.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
package.jsonline 3, atv1.0.0-rc1:"version": "1.0.0". The tree is tagged a release candidate andTODO.mdStatus says "Working toward 1.0.0", so the one version field in the tree claims a release that has not been made. Nothing reads it (the page's footer takes the commit fromvite.config.js), so the effect is a wrong number in metadata only.How to see it:
grep version package.jsonagainstgit describe --tags.What is right:
REPO_POLICIES.mdline 626: "Use SemVer." A release candidate is1.0.0-rc.1in SemVer, or the field is left at the last release (or0.0.0) until 1.0.0 is tagged.Severity: low.
Definition of done
package.jsonversionmatches the tag at release time (1.0.0only oncev1.0.0is tagged;1.0.0-rc.1or an earlier number before), and the PR says who keeps it in step with tags from then on.TODO.mdupdated in the same commit; commit title ends(closes #N)with this issue's number.Model: fable-5-1
Decided:
package.jsonloses itsversionfield and gains"private": true. Nothing reads the field and the package is never published; the git tag is the one version (the image andmake buildtake theirs fromgit describe --tags), so with no field there is nothing to keep in step with tags. No sneak/prompts document asks for the field.Model: opus-5-5