The archie-core GitHub mirror currently lists zero Actions secrets and variables (DEPLOY_TOKEN, RELEASE_SIGNING_KEY, CANARY_URL/CANARY_TOKEN/CANARY_WINDOW are all absent), so the release workflow (run 41474560617, queued, no jobs scheduled) will fail at its push step and the canary steps have nothing to run with. Tags v1.57.0+ exist only on the Gitea side. Done when the mirror's Actions configuration carries the release/deploy secrets (values stay CI-only) and a dispatched release run completes and pushes the version tag.
The archie-core GitHub mirror currently lists zero Actions secrets and variables (DEPLOY_TOKEN, RELEASE_SIGNING_KEY, CANARY_URL/CANARY_TOKEN/CANARY_WINDOW are all absent), so the release workflow (run 41474560617, queued, no jobs scheduled) will fail at its push step and the canary steps have nothing to run with. Tags v1.57.0+ exist only on the Gitea side. Done when the mirror's Actions configuration carries the release/deploy secrets (values stay CI-only) and a dispatched release run completes and pushes the version tag.
sam
added the bug label 2026-11-02 15:51:05 +00:00
Root cause found: the queued release run and missing secrets were on the GitHub mirror, a duplicate CI surface. Gitea Actions is the sole CI now: Actions disabled on samcharles93/archie-core; on git.catlow.cloud, quality run 1262 and deploy run 1261 on 796bfd00 are green, canary runs on schedule, and the archie-quality runner is online. Gitea secrets today: CANARY_TOKEN, RELEASE_SIGNING_KEY; variable CANARY_URL. To cut releases from Gitea (dispatch release.yml on git.catlow.cloud) DEPLOY_TOKEN must be added as a Gitea Actions secret on sam/archie — that value stays CI-only. Done when a release dispatched on Gitea cuts the version tag and pushes it from Gitea.
Root cause found: the queued release run and missing secrets were on the GitHub mirror, a duplicate CI surface. Gitea Actions is the sole CI now: Actions disabled on samcharles93/archie-core; on git.catlow.cloud, quality run 1262 and deploy run 1261 on 796bfd00 are green, canary runs on schedule, and the archie-quality runner is online. Gitea secrets today: CANARY_TOKEN, RELEASE_SIGNING_KEY; variable CANARY_URL. To cut releases from Gitea (dispatch release.yml on git.catlow.cloud) DEPLOY_TOKEN must be added as a Gitea Actions secret on sam/archie — that value stays CI-only. Done when a release dispatched on Gitea cuts the version tag and pushes it from Gitea.
release.yml now checks DEPLOY_TOKEN before checkout and fails with a named error, so a mirror without it no longer reads as a broken release (85b21578). RELEASING.md now lists every secret and variable a mirror needs and which workflow reads each.
Two things are still open:
The secrets themselves. The mirror carries none of DEPLOY_TOKEN, RELEASE_SIGNING_KEY, CANARY_TOKEN, or the CANARY_URL/CANARY_WINDOW variables. That is a GitHub settings action; values stay CI-only.
The run may still queue.release.yml is runs-on: self-hosted, and a mirror with no self-hosted runner queued the run with no jobs scheduled — which is what run 41474560617 shows. Setting secrets alone would leave it queued. Register a runner on the mirror, or cut releases from the Gitea primary only.
Done when a dispatched release run on the mirror gets past checkout and pushes its tag.
`release.yml` now checks `DEPLOY_TOKEN` before checkout and fails with a named error, so a mirror without it no longer reads as a broken release (85b21578). `RELEASING.md` now lists every secret and variable a mirror needs and which workflow reads each.
Two things are still open:
- **The secrets themselves.** The mirror carries none of `DEPLOY_TOKEN`, `RELEASE_SIGNING_KEY`, `CANARY_TOKEN`, or the `CANARY_URL`/`CANARY_WINDOW` variables. That is a GitHub settings action; values stay CI-only.
- **The run may still queue.** `release.yml` is `runs-on: self-hosted`, and a mirror with no self-hosted runner queued the run with no jobs scheduled — which is what run 41474560617 shows. Setting secrets alone would leave it queued. Register a runner on the mirror, or cut releases from the Gitea primary only.
Done when a dispatched release run on the mirror gets past checkout and pushes its tag.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The archie-core GitHub mirror currently lists zero Actions secrets and variables (DEPLOY_TOKEN, RELEASE_SIGNING_KEY, CANARY_URL/CANARY_TOKEN/CANARY_WINDOW are all absent), so the release workflow (run 41474560617, queued, no jobs scheduled) will fail at its push step and the canary steps have nothing to run with. Tags v1.57.0+ exist only on the Gitea side. Done when the mirror's Actions configuration carries the release/deploy secrets (values stay CI-only) and a dispatched release run completes and pushes the version tag.
Root cause found: the queued release run and missing secrets were on the GitHub mirror, a duplicate CI surface. Gitea Actions is the sole CI now: Actions disabled on samcharles93/archie-core; on git.catlow.cloud, quality run 1262 and deploy run 1261 on
796bfd00are green, canary runs on schedule, and the archie-quality runner is online. Gitea secrets today: CANARY_TOKEN, RELEASE_SIGNING_KEY; variable CANARY_URL. To cut releases from Gitea (dispatch release.yml on git.catlow.cloud) DEPLOY_TOKEN must be added as a Gitea Actions secret on sam/archie — that value stays CI-only. Done when a release dispatched on Gitea cuts the version tag and pushes it from Gitea.release.ymlnow checksDEPLOY_TOKENbefore checkout and fails with a named error, so a mirror without it no longer reads as a broken release (85b21578).RELEASING.mdnow lists every secret and variable a mirror needs and which workflow reads each.Two things are still open:
DEPLOY_TOKEN,RELEASE_SIGNING_KEY,CANARY_TOKEN, or theCANARY_URL/CANARY_WINDOWvariables. That is a GitHub settings action; values stay CI-only.release.ymlisruns-on: self-hosted, and a mirror with no self-hosted runner queued the run with no jobs scheduled — which is what run 41474560617 shows. Setting secrets alone would leave it queued. Register a runner on the mirror, or cut releases from the Gitea primary only.Done when a dispatched release run on the mirror gets past checkout and pushes its tag.
Obsolete: Actions is disabled on the GitHub mirror and releases run on Gitea. Release run 1880 there pushed v1.61.0 and its tag.