From 4635b0eb36effc022c7c400c1eaad7e95e364344 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 5 Jun 2026 20:42:32 +0200 Subject: [PATCH] Close Gitea PyPI publication workplan --- .../ISSUE-WP-0002-gitea-pypi-publication.md | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/workplans/ISSUE-WP-0002-gitea-pypi-publication.md b/workplans/ISSUE-WP-0002-gitea-pypi-publication.md index 65b522a..83c6854 100644 --- a/workplans/ISSUE-WP-0002-gitea-pypi-publication.md +++ b/workplans/ISSUE-WP-0002-gitea-pypi-publication.md @@ -4,11 +4,11 @@ type: workplan title: "Publish issue-core to Gitea PyPI" domain: custodian repo: issue-core -status: blocked +status: finished owner: codex topic_slug: custodian created: "2026-05-23" -updated: "2026-05-23" +updated: "2026-06-05" state_hub_workstream_id: "87a5dcb6-5b2c-4d3f-8d5c-e265889b0fc6" --- @@ -22,7 +22,7 @@ instead of a sibling checkout path. ```task id: ISSUE-WP-0002-T01 -status: blocked +status: done priority: high state_hub_task_id: "f0df7dbc-b55d-4835-a528-f44a329efb0e" ``` @@ -40,15 +40,15 @@ specific operator workstation and forces non-portable BuildKit named contexts. package registry secrets exist. - `docs/package-release.md` documents local and tag-based publishing. -**Blocker.** Publishing requires a Gitea package username/token with permission -to upload to: +**Resolved blocker.** Publishing required a Gitea package username/token with +permission to upload to: ```text https://gitea.coulomb.social/api/packages/coulomb/pypi ``` -No publish credentials are currently available in the shell or standard package -config files. +The package was published on 2026-06-05 using the operator-provided token from +`/tmp/gat.tmp`; the token value was not written to repo files or command logs. **Implementation steps.** @@ -81,3 +81,11 @@ config files. - The publish workflow has the required secrets and a documented release path. - The Railiance app deployment blocker can be closed without relying on local path dependencies. + +**Completed 2026-06-05.** Built and checked `issue-core==0.2.0`, published the +wheel and source distribution to the Coulomb Gitea PyPI registry as `tegwick` +through a temporary local Kubernetes port-forward, then exposed the approved +public `/api/packages` ingress route from `railiance-forge`. The public +package-specific simple index returns `200`, a clean temporary environment can +install `issue-core==0.2.0` from Gitea, and `vergabe-teilnahme/uv.lock` now +resolves `issue-core` from the Gitea registry instead of a sibling checkout.