README.md, first section, says: "The current version is pre-1.0 and while the repo was published in 2022, there has not yet been any versioned release. SemVer will be used for releases." v1.0.0-rc1 is tagged on that text and v1.0.0 would be too, so the first thing a reader of the released README learns is that no release exists. The paragraph after it, on where mfer version gets its number, stays right.
Reproduce on v1.0.0-rc1: git show v1.0.0-rc1:README.md | grep -n 'pre-1.0'.
Correct: the README says that releases are git tags named by SemVer, v1.0.0 the first, and nothing in it calls the project pre-1.0 or unreleased. It lands on next before v1.0.0 is tagged.
Severity: minor
Definition of done
No failing test: the change is to prose only.
README.md says the above, formatted with make fmt.
make check passes.
Model: fable-5-1
`README.md`, first section, says: "The current version is pre-1.0 and while the repo was published in 2022, there has not yet been any versioned release. SemVer will be used for releases." `v1.0.0-rc1` is tagged on that text and `v1.0.0` would be too, so the first thing a reader of the released README learns is that no release exists. The paragraph after it, on where `mfer version` gets its number, stays right.
Reproduce on `v1.0.0-rc1`: `git show v1.0.0-rc1:README.md | grep -n 'pre-1.0'`.
Correct: the README says that releases are git tags named by SemVer, `v1.0.0` the first, and nothing in it calls the project pre-1.0 or unreleased. It lands on `next` before `v1.0.0` is tagged.
Severity: minor
## Definition of done
- No failing test: the change is to prose only.
- `README.md` says the above, formatted with `make fmt`.
- `make check` passes.
Model: fable-5-1
clawbot
self-assigned this 2026-10-14 02:22:00 +02:00
Plan: built as the issue says: the first section of README.md says releases are git tags named by SemVer, v1.0.0 the first, and nothing in it calls the project pre-1.0 or unreleased. One PR to next through an independent review that checks every changed sentence against the tree. Worker rules: #99 (comment), without the TODO.md step.
Model: opus-5-5
Plan: built as the issue says: the first section of `README.md` says releases are git tags named by SemVer, `v1.0.0` the first, and nothing in it calls the project pre-1.0 or unreleased. One PR to `next` through an independent review that checks every changed sentence against the tree. Worker rules: https://git.eeqj.de/sneak/mfer/issues/99#issuecomment-115880, without the `TODO.md` step.
Model: opus-5-5
Built in #231: the README now says releases are git tags named by SemVer, starting with v1.0.0, in the paragraph on where mfer version gets its number. The old pre-1.0 paragraph is gone, and nothing else in the README calls the project unreleased.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/mfer/pulls/231: the README now says releases are git tags named by SemVer, starting with `v1.0.0`, in the paragraph on where `mfer version` gets its number. The old pre-1.0 paragraph is gone, and nothing else in the README calls the project unreleased.
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.
README.md, first section, says: "The current version is pre-1.0 and while the repo was published in 2022, there has not yet been any versioned release. SemVer will be used for releases."v1.0.0-rc1is tagged on that text andv1.0.0would be too, so the first thing a reader of the released README learns is that no release exists. The paragraph after it, on wheremfer versiongets its number, stays right.Reproduce on
v1.0.0-rc1:git show v1.0.0-rc1:README.md | grep -n 'pre-1.0'.Correct: the README says that releases are git tags named by SemVer,
v1.0.0the first, and nothing in it calls the project pre-1.0 or unreleased. It lands onnextbeforev1.0.0is tagged.Severity: minor
Definition of done
README.mdsays the above, formatted withmake fmt.make checkpasses.Model: fable-5-1
Plan: built as the issue says: the first section of
README.mdsays releases are git tags named by SemVer,v1.0.0the first, and nothing in it calls the project pre-1.0 or unreleased. One PR tonextthrough an independent review that checks every changed sentence against the tree. Worker rules: #99 (comment), without theTODO.mdstep.Model: opus-5-5
Built in #231: the README now says releases are git tags named by SemVer, starting with
v1.0.0, in the paragraph on wheremfer versiongets its number. The old pre-1.0 paragraph is gone, and nothing else in the README calls the project unreleased.Model: opus-5-5