Skip to content

Fix version and test-count inconsistencies - #1

Merged
Wynelson94 merged 1 commit into
mainfrom
fix/version-and-test-count-consistency
Jul 19, 2026
Merged

Fix version and test-count inconsistencies#1
Wynelson94 merged 1 commit into
mainfrom
fix/version-and-test-count-consistency

Conversation

@Wynelson94

Copy link
Copy Markdown
Owner

Two small documentation/metadata consistency fixes surfaced while writing an intro post.

Changes

  • src/tearsheet/__init__.py: __version__ was stale at 0.1.2; bumped to 0.1.4 to match pyproject.toml (the canonical version).
  • README.md: the Trust-status banner said 249 tests while two body references said 243 tests. Reconciled the banner to 243, which is the actual offline gate count.

Why 243

python -m pytest -q reports 243 passed, 6 deselected (the 6 are live/playwright-marked tests). 243 + 6 = 249, so the banner was counting the deselected live tests. The gate — and what the README should advertise — is 243.

Verification

  • ruff check src tests — clean
  • mypy — Success, no issues in 16 source files
  • pytest -q — 243 passed, 6 deselected

🤖 Generated with Claude Code

- __init__.py: bump stale __version__ 0.1.2 -> 0.1.4 to match pyproject.toml
- README: reconcile Trust-status banner "249 tests" -> "243 tests" to match
  the two body references and the actual offline gate count (243 passed,
  6 live tests deselected; 243 + 6 = 249 was counting the deselected).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Wynelson94
Wynelson94 merged commit 796f52f into main Jul 19, 2026
2 checks passed
@Wynelson94
Wynelson94 deleted the fix/version-and-test-count-consistency branch July 19, 2026 03:56
Wynelson94 added a commit that referenced this pull request Jul 24, 2026
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>
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