Close Gitea PyPI publication workplan

This commit is contained in:
2026-06-05 20:42:32 +02:00
parent d703463f16
commit 4635b0eb36

View File

@@ -4,11 +4,11 @@ type: workplan
title: "Publish issue-core to Gitea PyPI" title: "Publish issue-core to Gitea PyPI"
domain: custodian domain: custodian
repo: issue-core repo: issue-core
status: blocked status: finished
owner: codex owner: codex
topic_slug: custodian topic_slug: custodian
created: "2026-05-23" created: "2026-05-23"
updated: "2026-05-23" updated: "2026-06-05"
state_hub_workstream_id: "87a5dcb6-5b2c-4d3f-8d5c-e265889b0fc6" state_hub_workstream_id: "87a5dcb6-5b2c-4d3f-8d5c-e265889b0fc6"
--- ---
@@ -22,7 +22,7 @@ instead of a sibling checkout path.
```task ```task
id: ISSUE-WP-0002-T01 id: ISSUE-WP-0002-T01
status: blocked status: done
priority: high priority: high
state_hub_task_id: "f0df7dbc-b55d-4835-a528-f44a329efb0e" 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. package registry secrets exist.
- `docs/package-release.md` documents local and tag-based publishing. - `docs/package-release.md` documents local and tag-based publishing.
**Blocker.** Publishing requires a Gitea package username/token with permission **Resolved blocker.** Publishing required a Gitea package username/token with
to upload to: permission to upload to:
```text ```text
https://gitea.coulomb.social/api/packages/coulomb/pypi https://gitea.coulomb.social/api/packages/coulomb/pypi
``` ```
No publish credentials are currently available in the shell or standard package The package was published on 2026-06-05 using the operator-provided token from
config files. `/tmp/gat.tmp`; the token value was not written to repo files or command logs.
**Implementation steps.** **Implementation steps.**
@@ -81,3 +81,11 @@ config files.
- The publish workflow has the required secrets and a documented release path. - The publish workflow has the required secrets and a documented release path.
- The Railiance app deployment blocker can be closed without relying on local - The Railiance app deployment blocker can be closed without relying on local
path dependencies. 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.