coulomb/kaizen-agentic
2
0
Fork 0
Code Issues 4 Pull Requests Actions Projects Releases Wiki Activity

fix: use build venv in Gitea publish workflow (PEP 668)
Some checks failed
ci / test (push) Failing after 37s
Details

Browse Source 
Haskelseed runner blocks system-wide pip installs. Create an isolated
.build-venv for build/twine and document workflow_dispatch API path.
This commit is contained in:
Bernd Worsch
2026-06-16 07:15:57 +02:00
parent 5ce3d0766e
commit 9d2bab9a38
2 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/PACKAGE_RELEASE.md
View File

@@ -72,10 +72,15 @@ invalid. Do not commit tokens to the repository.
Verify secrets without cutting a release:
1. Open **Actions → Publish Python package → Run workflow** (`workflow_dispatch`)
1. Open **Actions → Publish Python package → Run workflow** (`workflow_dispatch`),
or dispatch via API:
`POST /api/v1/repos/coulomb/kaizen-agentic/actions/workflows/publish-python-package.yml/dispatches`
with body `{"ref":"main"}`
2. Confirm the run completes and `twine upload` succeeds
3. Optional: `pip install kaizen-agentic==<version> --extra-index-url ...`
The publish job uses an isolated `.build-venv` on the runner (PEP 668 safe).
## Pre-tag release checklist
Before `git tag vX.Y.Z && git push origin vX.Y.Z`: