Tier 0 of the post-1.3.0 roadmap. Target version: 1.3.1 (patch).
Small, uncontroversial, no public API change — and one of them is a
live risk. Nothing here depends on anything else; all five can go in
parallel.
| # | Item |
|---|
| #78 | Gate the release workflow on the CI jobs |
| #79 | Enforce the coverage level already achieved |
| #80 | Align the layer sub-package exports with the top-level package |
| #81 | Correct the stale corpus figure and layout map in ARCHITECTURE.md |
| #109 | The README Roadmap section advertises shipped work as upcoming |
Why 1.3.1 and not 1.4.0
No behaviour changes for anyone consuming the public API. #80 adds
exports that were arguably always meant to be there; if that is judged
a feature rather than a fix, it moves to 1.4.0 and the rest still ships
as a patch.
Do #78 first
release.yml publishes to PyPI on a v* tag with no dependency on
lint, typecheck or tests. Until that is fixed, every release in this
roadmap — including 1.3.1 itself — is unguarded, and a published
version can only be yanked, never replaced.
#81 and #109 are the same bug in two places
Documentation duplicating facts that live elsewhere, then drifting. The
corpus count is stated in three files and wrong in one; the README
roadmap re-lists tracker items and went stale when they shipped. Both
fixes should reduce duplication rather than just correct the current
values.
Part of the post-1.3.0 roadmap: #107
Tier 0 of the post-1.3.0 roadmap. Target version: 1.3.1 (patch).
Small, uncontroversial, no public API change — and one of them is a
live risk. Nothing here depends on anything else; all five can go in
parallel.
Why 1.3.1 and not 1.4.0
No behaviour changes for anyone consuming the public API. #80 adds
exports that were arguably always meant to be there; if that is judged
a feature rather than a fix, it moves to 1.4.0 and the rest still ships
as a patch.
Do #78 first
release.ymlpublishes to PyPI on av*tag with no dependency onlint, typecheck or tests. Until that is fixed, every release in this
roadmap — including 1.3.1 itself — is unguarded, and a published
version can only be yanked, never replaced.
#81 and #109 are the same bug in two places
Documentation duplicating facts that live elsewhere, then drifting. The
corpus count is stated in three files and wrong in one; the README
roadmap re-lists tracker items and went stale when they shipped. Both
fixes should reduce duplication rather than just correct the current
values.
Part of the post-1.3.0 roadmap: #107