The first live run of daedalus publish on the v0.12.0 release was
rejected by its own tag guard: git describe --exact-match returns
whichever name git picks (here: latest), not the version tag, when
several tags share the release commit. The guard now checks that
v<version> is among git tag --points-at HEAD; moving tags on the
same commit are fine (publish spec 3.3.2, reproduced by a new test).
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
- new script python/src/publish/publish.py: guards (clean tree,
HEAD exactly tagged v<version>, version not yet on PyPI,
build+twine present), then the chained python -m build (the
sdist must rebuild the wheel, SPEC 9.2.1) and twine check;
--upload sends exactly this version's sdist+wheel, credentials
stay with twine (~/.pypirc or prompt, __token__)
- spec python/src/publish/spec.md (sections 1-7) first, then
tests (13) in python/tests/test_publish.py, then code
(SPEC 6.12)
- fix release-blocking sdist defect (SPEC 9.2.1): empty
powershell/ and batch/ folders now carry README placeholders
and MANIFEST.in ships them, so an sdist installs again
- release tooling in requirements.txt; registry entry, README
row + section, CHANGELOG 0.12.0, version pins
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>