feat: daedalus publish - guarded PyPI release (v0.12.0)

- 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>
This commit is contained in:
nvaldez
2026-11-19 10:27:57 +01:00
parent 41c8b99bd6
commit 7ebce2109e
14 changed files with 634 additions and 3 deletions
+8
View File
@@ -637,6 +637,14 @@ autotest results
| `powershell/` | `daedalus/_library/powershell/` | `*.ps1` |
| `batch/` | `daedalus/_library/batch/` | `*.bat` |
- **9.2.1** The source tree must be able to rebuild its wheel from
the sdist: every folder the packaging declares (including empty
`powershell/` and `batch/`) carries at least a `README.md`
placeholder, and `MANIFEST.in` ships both folders in the sdist.
A missing declared package directory is a release-blocking
defect: `python -m build` builds sdist and wheel chained, so a
broken sdist fails the release before it ships.
- **9.3** `LIBRARY_ROOT` is `PACKAGE_DIR/_library` when that folder exists
(a normal install), otherwise `REPO_ROOT` (a checkout or an editable
install).