Skip to content

fix(docs): stop the README announcing an old release as current - #77

Merged
arthware-dev merged 1 commit into
mainfrom
chore/version-consistency
Sep 10, 2026
Merged

arthware-dev merged 1 commit into
mainfrom
chore/version-consistency

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

The README told every visitor v0.3.0-beta.1 was the current beta, long after
beta.2 shipped. It is the first file anyone reads and the only version-bearing
one nothing verified, so the release check now covers it alongside the CLI and
pyproject versions.

Other version mentions there are historical and stay put; the check targets
the sentence claiming which release is current.

The README told every visitor v0.3.0-beta.1 was the current beta, four
months after beta.2 shipped. It is the first file anyone reads and the
only version-bearing one nothing verified, so the release check now
covers it alongside the CLI and pyproject versions.

Other version mentions in the README are historical and stay put; the
check targets the sentence that claims which release is current, and
fails loudly if that sentence is ever reworded away.
@arthware-dev
arthware-dev merged commit 120e729 into main Sep 10, 2026
1 check passed
@arthware-dev
arthware-dev deleted the chore/version-consistency branch September 22, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant