chore: v0.1.5 — name the release the README already referenced - #4
Merged
Conversation
The stub-extraction guard (#3) shipped with README text reading "Since v0.1.5", while pyproject.toml and __init__.py still said 0.1.4 and the CHANGELOG carried the guard under [Unreleased]. That is the same version-drift class PR #1 was opened to fix, reintroduced in the same day. Bumps both manifests, promotes [Unreleased] to [0.1.5], and adds the link ref pointing at 32858dd. The rest of the [Unreleased] block (MIT LICENSE, CI gate, synthetic FP fixture, UA correction) also shipped after 0.1.4, so it moves under 0.1.5 with the guard rather than lingering as unreleased. No git tags exist in this repo, so CHANGELOG links continue to point at shipping commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Wynelson94
added a commit
that referenced
this pull request
Jul 24, 2026
Two maintenance items from the 2026-07-24 audit.
1. Actions bump. actions/checkout@v4 and actions/setup-python@v5 target
Node 20; runners now force them onto Node 24 and print a deprecation
warning on every run. v6 is the native pair. (longhand already runs
v6/v6 for the same reason.)
2. Consistency gate. Prose-vs-code drift has shipped here twice and both
times nothing but a manual read caught it:
PR #1 "Fix version and test-count inconsistencies"
PR #4 README said "Since v0.1.5" while pyproject and __init__ said
0.1.4 and the CHANGELOG had the change under [Unreleased]
scripts/check_consistency.py asserts, against pyproject as canonical:
__init__.__version__ agrees; CHANGELOG has a RELEASED section for that
version (the check that would have caught PR #4); and every "N tests"
claim in the README equals what pytest actually collects.
It found live drift on its first run: the README claimed 243 tests in
three places while the suite is 247 since the stub guard landed. Fixed
here.
Falsified in both directions before committing — corrupting the test
count, the version, and the CHANGELOG section each produce exit 1 with
the specific line; restoring produces exit 0.
Gate is now: ruff check src tests scripts && mypy && pytest &&
check_consistency.py. CONTRIBUTING and CI updated to match.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Self-inflicted, same-day. PR #3 shipped the stub-extraction guard with README text reading "Since v0.1.5 a
warning:line fires…" — butpyproject.tomland__init__.pyboth still said0.1.4, and the CHANGELOG carried the guard under[Unreleased]. So the README referenced a version that didn't exist anywhere.That's the exact drift class PR #1 ("Fix version and test-count inconsistencies") was opened to fix, reintroduced hours later. Caught by a consistency sweep, not by the gate — nothing enforces it.
What changed
pyproject.tomlandsrc/tearsheet/__init__.py:0.1.4→0.1.5[Unreleased]promoted to[0.1.5] — 2026-07-24, with a fresh empty[Unreleased]above it[0.1.5]link ref pointing at32858dd; repointed[Unreleased]'s compare baseThe rest of the old
[Unreleased]block (MIT LICENSE, CI gate, synthetic FP fixture, UA correction) also shipped after 0.1.4, so it moves under 0.1.5 with the guard rather than lingering.No git tags exist in this repo, so CHANGELOG links keep pointing at shipping commits — consistent with the existing
<!-- No git tags are cut yet -->note.Verification
grepfor0.1.4/0.1.5across README, CHANGELOG, pyproject,__init__— README's "since v0.1.5" claim is now true; remaining0.1.4references are historical CHANGELOG/README entries, which are correct as written.ruff check,mypy(16 files), 247 passed / 6 deselected.Worth considering separately
This repo has zero git tags across five released versions. A
check_version_sync.py-style script (longhand has one) or a CI step asserting pyproject/__init__/README agree would make this class impossible rather than caught-by-luck twice.🤖 Generated with Claude Code