Repository navigation
Fixed
-
A release could be reported as failed after publishing successfully. 2.4.1 uploaded to
PyPI and was then failed by its own confirmation step, which skipped the tag and the
release page and left the release to be finished by hand. Two causes, both fixed.The confirmation polled for sixty seconds. PyPI took longer. It now waits five minutes.
It also asked one endpoint. For a few minutes after an upload PyPI's CDN serves
inconsistent answers and which view updates first varies by edge node: 2.4.0 appeared on
the per-version document while the simple index still omitted it, and 2.4.1 did the exact
reverse. Both are now asked and either is accepted. -
The publish job can be re-run.
twine uploadgained--skip-existingand the tagging
step no longer fails on a tag that already exists, so a failure in any step after the
upload can be retried instead of needing the tag and release page created manually. The
release gate also runs the same four checks as CI, which it had drifted from.
Changed
-
ruffis now the only formatter and linter.blackandisortwere configured alongside
it and disagreed with it —isortwrapped at 88 columns,ruffdeclared 100 — andruff
already did both jobs, with import sorting selected through its"I"rules. The tree is
reformatted once at 100 columns, the widthruffwas already configured for, and
ruff format --checkis a CI gate from here on so it cannot drift again.Nothing in the aquarium changed. Every shape and colour mask in the package was hashed
before and after the reformat and is byte-identical, which matters more here than usual: a
formatter that rewrapped a fish would break the rendering silently and no test would catch it.
pipx install asciiquarium==2.4.2