Release 0.2.1

[npstorey]

Release 0.2.1 (npstorey/typedstandards#141, P5; the owner's rulings P4-1 and P4-2 = A, 2026-10-09).

What changes

One commit, 553ec14c9065ac2de7a686d33b98629fb842cb24, on main at c1287a8 (the P5 merge). It is SSH-signed with a sign-off and changes two lines:

• src/typedstandards/__init__.py: __version__ moves from 0.2.0 to 0.2.1. It is a patch release: no export changes.
• CHANGELOG.md: ## Unreleased becomes ## 0.2.1 — 2026-10-10, the publish day. The entries are verbatim.

uv.lock is unchanged: the version is dynamic, as at 0.1.1 and 0.2.0. The CLI pin stays at 0.2.0.

Checks (ORCH, at 553ec14)

uv sync --locked; uv run pytest   -> 392 passed, 1 skipped
uv run ruff check .               -> All checks passed!
gitleaks git --log-opts=origin/main..HEAD -> no leaks found

The publish dry run, rehearsed in a throwaway worktree at 553ec14, with RELEASE_REF pointed at this branch so its main check had a target:

Checking dist/typedstandards-0.2.1-py3-none-any.whl: PASSED
Checking dist/typedstandards-0.2.1.tar.gz: PASSED
publish: the wheel vendors @typedstandards/cli 0.2.0 (232 files)
smoke check passed
publish: PyPI still answers 404 for typedstandards 0.2.1
publish:   b14372f7e4dadccab5d5c2b6ce7fb9e7376556b416c5d56b67565ac0295d2a44  typedstandards-0.2.1.tar.gz
publish:   4823233cb3baf485bfcc87c399f904e44234332d2ed44502ef246fd0d103a453  typedstandards-0.2.1-py3-none-any.whl
publish: DRY_RUN: nothing was uploaded.
exit 0

After the merge

The owner publishes on 2026-10-10, the CHANGELOG's date, which publish.sh's live run checks. The publish runs from a detached worktree at this PR's merge commit, with scripts/publish.sh under op run and the project-scoped token: DRY_RUN=1 first, then the live run, which reads the release back from PyPI.

🤖 Generated with Claude Code