The first section of README.md said the project had no versioned release. It now says releases are git tags named by SemVer and names the first one, as #226 asks.
The new sentence opens the paragraph on where mfer version gets its number, in place of that paragraph's old opening sentence, "A version is a git tag", which it covers. The rest of that paragraph is unchanged. The removed paragraph also said the repo was published in 2022; the README's first paragraph already says so.
Nothing else in README.md says the project is unreleased.
No new files; README.md is the only file changed.
Judgement call: the README names the first release by a tag that does not exist yet. It becomes true when that tag is cut from this tree, which is what the issue asks for. The release-candidate tag already on the repo is not called a release.
The first section of `README.md` said the project had no versioned release. It now says releases are git tags named by SemVer and names the first one, as https://git.eeqj.de/sneak/mfer/issues/226 asks.
The new sentence opens the paragraph on where `mfer version` gets its number, in place of that paragraph's old opening sentence, "A version is a git tag", which it covers. The rest of that paragraph is unchanged. The removed paragraph also said the repo was published in 2022; the README's first paragraph already says so.
Nothing else in `README.md` says the project is unreleased.
No new files; `README.md` is the only file changed.
Judgement call: the README names the first release by a tag that does not exist yet. It becomes true when that tag is cut from this tree, which is what the issue asks for. The release-candidate tag already on the repo is not called a release.
Closes https://git.eeqj.de/sneak/mfer/issues/226
Model: opus-5-5
The first section of the README said the project had no versioned
release. It now says releases are git tags named by SemVer and names
the first one. That sentence opens the paragraph on where `mfer
version` gets its number, in place of its old opening sentence, "A
version is a git tag", which the new one covers. The rest of that
paragraph is unchanged and still matches `script/build`,
`script/docker` and the `Dockerfile`.
Model: opus-5-5
Judgement call: the README names v1.0.0 as the first release although the tag v1.0.0-rc1 already exists; I read a release-candidate tag as not a release, as SemVer calls it a pre-release.
Model: opus-5-5
Review passed.
Judgement call: the README names `v1.0.0` as the first release although the tag `v1.0.0-rc1` already exists; I read a release-candidate tag as not a release, as SemVer calls it a pre-release.
Model: opus-5-5
clawbot
merged commit 06127e291f into next2026-10-15 22:42:35 +02:00
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.
The first section of
README.mdsaid the project had no versioned release. It now says releases are git tags named by SemVer and names the first one, as #226 asks.The new sentence opens the paragraph on where
mfer versiongets its number, in place of that paragraph's old opening sentence, "A version is a git tag", which it covers. The rest of that paragraph is unchanged. The removed paragraph also said the repo was published in 2022; the README's first paragraph already says so.Nothing else in
README.mdsays the project is unreleased.No new files;
README.mdis the only file changed.Judgement call: the README names the first release by a tag that does not exist yet. It becomes true when that tag is cut from this tree, which is what the issue asks for. The release-candidate tag already on the repo is not called a release.
Closes #226
Model: opus-5-5
Review passed.
Judgement call: the README names
v1.0.0as the first release although the tagv1.0.0-rc1already exists; I read a release-candidate tag as not a release, as SemVer calls it a pre-release.Model: opus-5-5