release: v0.1.3

[cmeans-claude-dev]

Summary

Cuts v0.1.3 — the first release that will exercise the new auto-release-page workflow end-to-end (PR #47, merged earlier today).

Bumps version in pyproject.toml 0.1.2 → 0.1.3, refreshes uv.lock, promotes ## [Unreleased] → ## [0.1.3] - 2026-04-28, and updates link refs at the bottom of CHANGELOG.md.

What's in v0.1.3

Five PRs since v0.1.2 (2026-04-27):

#	Type	Title
#41	fix	fix(workflow): insert ### Changed in Keep-a-Changelog order on auto-CHANGELOG (closes #26)
#44	chore	chore(docker): bump uv pin from ==0.4.* to >=0.5,<1 (closes #34)
#45	docs	docs(issue-template): refactor bug_report version placeholder to durable form (closes #40)
#46	docs	docs(readme): refresh dogfood blockquote — count > 0, drop M3 reference (closes #43)
#47	ci	ci(publish): auto-create GitHub release page on v* tag from CHANGELOG

No runtime collector / badge code changes — all CI / docs / packaging hygiene plus the new release-page automation.

After merge

1. Tag v0.1.3 at the merge commit and push.
2. Watch publish.yml — should run build (with the new awk extractor / artifact upload), then publish to PyPI via OIDC, then release (auto-create the GitHub release page from the v0.1.3 CHANGELOG section).
3. Verify the auto-created release page body matches ## [0.1.3] - 2026-04-28 verbatim, and that PyPI ships pypi-winnow-downloads==0.1.3.

Test plan

• Local uv run pytest --cov → 71 passed, 100% coverage (verified pre-push)
• Local uv run ruff check src/ tests/ and uv run ruff format --check src/ tests/ → clean (verified pre-push)
• Local uv run mypy src/pypi_winnow_downloads/ → no issues (verified pre-push)
• Local uv build → produces pypi_winnow_downloads-0.1.3-py3-none-any.whl + sdist (verified pre-push)
• CI lint / typecheck / test (3.11/3.12/3.13) / deploy-smoke all green
• After merge: tag push triggers publish.yml; PyPI ship + auto-release-page both succeed

🤖 Generated with Claude Code

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cmeans]

LGTM

[cmeans]

QA Round 1 — PASS

Release mechanic verification at head cc9143c. Documentation/packaging-only patch; SemVer patch fit (no public-API delta). Local + CI all green.

Diff scope (3 files, minimal)

File	Change
pyproject.toml	version = "0.1.2" → "0.1.3" (single line)
uv.lock	package's own version = "0.1.2" → "0.1.3" (single line, no incidental dep churn)
CHANGELOG.md	## [0.1.3] - 2026-04-28 heading inserted after empty ## [Unreleased]; existing Added/Fixed bullets become attributed to v0.1.3; [Unreleased] link ref updated to v0.1.3...HEAD; new [0.1.3] ref added comparing v0.1.2...v0.1.3

Local verification

Check	Result
uv run pytest --cov	71 passed, 100% coverage on src/, fail_under = 100 gate honored
uv run ruff check / format --check	clean
uv run mypy src/	no issues
uv build	both pypi_winnow_downloads-0.1.3-py3-none-any.whl and pypi_winnow_downloads-0.1.3.tar.gz
import pypi_winnow_downloads; __version__ post-install	0.1.3

CI green at cc9143c (lint, typecheck, test 3.11/3.12/3.13, deploy-smoke).

v0.1.3 contents cross-check

PR body claims five PRs since v0.1.2; git log v0.1.2..pr-48 --oneline shows exactly those plus the release commit (#41 / #44 / #45 / #46 / #47 + release: v0.1.3). All five represented in the new [0.1.3] section:

• ### Added: PR #47 (auto-release-page workflow)
• ### Fixed: closes #34 (PR #44, Dockerfile uv pin), closes #40 (PR #45, bug_report placeholder), closes #43 (PR #46, README dogfood), closes #26 (PR #41, KaC ordering)

First exercise of #47's auto-release-page workflow

This release will trigger the PR #47 workflow end-to-end on tag push. Pre-running the new awk extractor against the v0.1.3 CHANGELOG section produces a 13-line, non-empty body (the ### Added/### Fixed blocks in this release), terminating cleanly before ## [0.1.2] - 2026-04-27. Empty-Unreleased extraction returns 0 lines (irrelevant to the v0.1.3 tag — the gate is parameterized on ${GITHUB_REF_NAME#v}). Build-job gate would pass; release-job would create the GitHub release page from the 13 captured lines.

Zero findings. Ready for QA Signoff.

[cmeans]

QA round 1 → Ready for QA Signoff.

Release mechanic clean: minimal-pair pyproject.toml + uv.lock bump (no incidental dep churn), CHANGELOG [Unreleased] → [0.1.3] - 2026-04-28 promotion with link refs updated, all five v0.1.2→v0.1.3 PRs (#41/#44/#45/#46/#47) accounted for in the new section. Local re-run: 71/71 pytest, 100% coverage, ruff/format/mypy clean, uv build produces both 0.1.3 artifacts, __version__ post-install is 0.1.3. CI all green at cc9143c.

This is the first release that will exercise PR #47's auto-release-page workflow end-to-end — pre-running the new awk extractor against the v0.1.3 CHANGELOG section produces a well-formed 13-line body. Build-job gate passes; release-job will create the page from those 13 lines.

Last checkbox (post-merge tag-push behavior) intentionally left unchecked — only verifiable on the actual v0.1.3 tag push.

Awaiting maintainer QA Approved.