Skip to content

Rename Pydantic Canary to Bumpcheck and strengthen comparisons - #6

Merged
smigolsmigol merged 2 commits into
mainfrom
feat/bumpcheck-migration
Aug 22, 2026
Merged

smigolsmigol merged 2 commits into
mainfrom
feat/bumpcheck-migration

Conversation

@smigolsmigol

Copy link
Copy Markdown
Owner

Summary

Rename Pydantic Canary to Bumpcheck before the old identity becomes established. This also closes two comparison gaps that could hide runtime drift: Python equality treated 1, 1.0, and true as equivalent, and Pydantic validation errors ignored field locations.

Changes

  • Rename the distribution, import package, and primary command to bumpcheck, while retaining a temporary pydantic-canary command alias.
  • Compare canonical JSON representations in top-level and batch results.
  • Compare stable Pydantic validation error type and loc records.
  • Keep worker result JSON separate from Python, native, and child-process output.
  • Replace the repository-only quickstart with a clean-directory workflow and document --with . for local projects.
  • Add a CI regression using Pydantic 2.10.6 and 2.11.1.

Validation

  • 61 unit tests pass on Python 3.10 through 3.14.
  • Branch coverage is 96%.
  • The real Pydantic 2.10.6 to 2.11.1 regression is detected.
  • The built wheel passes metadata and contents checks.
  • Tracewright's four-record JSONL consumer remains unchanged across Pydantic 2.10.0 and 2.13.4.

Repository rename and PyPI publication are deliberately not part of this PR.

@smigolsmigol
smigolsmigol marked this pull request as ready for review August 22, 2026 21:33
@smigolsmigol
smigolsmigol merged commit f396dc5 into main Aug 22, 2026
11 checks passed
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