Repository navigation
Docket 0.1.5
[0.1.5] - 2026-10-19
Fixed
- The published long description carries the mark. The 0.1.4 wheel and sdist were built from
the commit before the README logo was committed, so the package page rendered the version and
the badges but no artwork.README.mdis the long description, and the two distributions of
0.1.4 froze it at that commit; re-uploading them under the same filenames is not possible,
because PyPI reserves a filename once it is published. 0.1.5 is built from the commit that
holds the logo, and the package page and the repository now agree.
Added
-
The README carries the horizontal lockup, in both schemes. A
<picture>with a
dark-mode<source>and a light<img>, 250x80, sitting above## Why Docket?. Both
targets are absolute and point at the documentation site, which is where the rest of the
README already points:README.mdis the PyPI long description, and PyPI resolves a relative
target againsthttps://pypi.org/project/docket-ai/, so a repo-relative logo would 404 on
the package page while resolving correctly on GitHub. That is the same defect the 29
markdown links already carried, and it took three releases to notice. -
The PyPI link guard now sees raw HTML.
INLINE_LINKmatches](target)only, so a raw
srcorsrcsetwas invisible to both halves oftests/test_doc_links.py; a logo pointed
at a relative path would have 404'd on PyPI unreported.HTML_ASSETreads thesrc,
srcsetandhrefattributes of anyimg,sourceorlinktag, and both guards use it.
Both halves were proven to fire on the defect they now name by injecting a relative logo
path and a dead absolute one into the README and watching the right guard fail.Measured on the published description rather than on the source: rendered through PyPI's own
readme_rendererand nh3 sanitiser, the 0.1.5 description carries 52hrefandsrc
attributes, 36 of them absolute, 0 relative, and all 30 distinct URLs answer 200.