Release 0.2.0

[npstorey]

Release 0.2.0 (npstorey/typedstandards#141, G5: the cut, ruled by the owner on 2026-10-09).

What changes

One commit, 4b441b4d2d7af7a773133043516299f54baa0277, on main at 656f025 (the P2 merge). It is SSH-signed with a sign-off and changes two lines:

• src/typedstandards/__init__.py: __version__ moves from 0.1.1 to 0.2.0, a minor bump for the new exports publish, publish_attestation, GitHubPagesHost, PublishError and PublishRefusedError.
• CHANGELOG.md: ## Unreleased becomes ## 0.2.0 — 2026-10-09, the publish day. The entries are verbatim.

uv.lock is unchanged: the package's version is dynamic, and its editable entry carries none. That is the same as 0.1.1's release commit, 19eb454. The CLI pin stays at 0.2.0. Nothing else names the package version: git grep 0.1.1 outside the lock files finds only the 0.1.1 CHANGELOG heading and one test's mention of host-core 0.1.1.

Checks (ORCH, at 4b441b4)

uv sync --locked; uv run pytest  -> 368 passed
uv run ruff check .              -> All checks passed!
uv build                         -> Successfully built dist/typedstandards-0.2.0.tar.gz
                                    Successfully built dist/typedstandards-0.2.0-py3-none-any.whl
gitleaks git --log-opts=656f025..HEAD -> no leaks found

After the merge

The owner publishes with scripts/publish.sh from a detached worktree at this PR's merge commit, under op run with the project-scoped PyPI token's reference: DRY_RUN=1 first, then the live run. Its read-back runs from PyPI.

🤖 Generated with Claude Code