From 9b4056bb28ab832e5a6ea4e0119c5895bf74a802 Mon Sep 17 00:00:00 2001 From: codex Date: Thu, 16 Jul 2026 14:45:57 +0200 Subject: [PATCH] CUST-WP-0059: T06 done (promote doc); T05 de-risked Co-Authored-By: Claude Opus 4.8 --- ...ST-WP-0059-forgejo-ci-publish-cutover-tail.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/workplans/CUST-WP-0059-forgejo-ci-publish-cutover-tail.md b/workplans/CUST-WP-0059-forgejo-ci-publish-cutover-tail.md index 7ede7c8..090b8a4 100644 --- a/workplans/CUST-WP-0059-forgejo-ci-publish-cutover-tail.md +++ b/workplans/CUST-WP-0059-forgejo-ci-publish-cutover-tail.md @@ -105,6 +105,13 @@ needs_human: true state_hub_task_id: "4a97eadb-7102-4658-b567-cc730e3ffaea" ``` +**De-risked 2026-07-16:** the Forgejo PyPI publish path is proven working — +issue-core resolves at `/api/packages/coulomb/pypi/simple/issue-core/` (`200`), +and `ubuntu-latest` is a registered Forgejo runner label. kaizen uses the +identical pattern + org secrets, so its publish is high-confidence; it just needs +its next `v*` tag to fire (kaizen simple index is `404` — nothing published since +cutover). Remaining confirmation: one green kaizen `ci` run + one tagged publish. + Confirm the new Forgejo workflows run end-to-end: (1) `FORGEJO_PYPI_USER` / `FORGEJO_PYPI_TOKEN` secrets are present (repo or org scope) on issue-core and kaizen-agentic; (2) the `ubuntu-latest` runner label resolves on Forgejo Actions; @@ -120,11 +127,18 @@ Forgejo `ci` run is green. ```task id: CUST-WP-0059-T06 -status: todo +status: done priority: medium state_hub_task_id: "7e75e9be-435d-4a8a-b5c5-340fe7e43772" ``` +**Done 2026-07-16:** promote-flow documented at +`state-hub/deploy/railiance/apps/charts/state-hub/PROMOTE.md` — CI publishes +`main-`+`latest` to Forgejo; promotions pin an immutable `main-` via +`helm upgrade --set image.tag=… --atomic` and bump chart `appVersion`. The chart +already defaults `image.repository` to Forgejo; the one-off `f2e042a` copy is +recorded, with the next promotion directed to move onto a `main-`. + The state-hub Helm chart `appVersion` and the deployed release pin `f2e042a` (gitea-era; manually copied to Forgejo on 2026-07-16 to fix the live pull). Forgejo CI produces `main-` + `latest`. Align the deployment/promotion convention to