The archipelago repo's GitHub mirror has only the ARCHIPELAGO_CATALOGUE_KEY Actions secret; DEPLOY_TOKEN is absent, so the publish workflow's skopeo login gets an empty password and the run fails (run 41474436585, 2026-11-02). Earlier publishes logged into ghcr.io with a masked password, so the workflow moved to the Gitea registry without the mirror secret being migrated. Done when a publish run on main reaches the registry login step with a non-empty credential and publishes the signed catalogue.
The archipelago repo's GitHub mirror has only the ARCHIPELAGO_CATALOGUE_KEY Actions secret; DEPLOY_TOKEN is absent, so the publish workflow's `skopeo login` gets an empty password and the run fails (run 41474436585, 2026-11-02). Earlier publishes logged into ghcr.io with a masked password, so the workflow moved to the Gitea registry without the mirror secret being migrated. Done when a publish run on main reaches the registry login step with a non-empty credential and publishes the signed catalogue.
sam
added the bug label 2026-11-02 15:51:05 +00:00
Root cause found: the failure email came from the GitHub mirror, which was running duplicate CI with no secrets. Gitea Actions is the real CI and already published successfully: publish run 1260 on 6f28cf9 (forge-gitea:1.2.0, forge-github:1.2.0, signed catalogue) is green on git.catlow.cloud. Actions are now disabled on the GitHub mirror (samcharles93/archipelago), so no runs or notification emails originate there. Remaining for Gitea-only operation: DEPLOY_TOKEN must exist as a Gitea Actions secret on sam/archipelago only if publish ever needs to run anywhere other than Gitea — it does not. Closing as resolved by the mirror change.
Root cause found: the failure email came from the GitHub mirror, which was running duplicate CI with no secrets. Gitea Actions is the real CI and already published successfully: publish run 1260 on 6f28cf9 (forge-gitea:1.2.0, forge-github:1.2.0, signed catalogue) is green on git.catlow.cloud. Actions are now disabled on the GitHub mirror (samcharles93/archipelago), so no runs or notification emails originate there. Remaining for Gitea-only operation: DEPLOY_TOKEN must exist as a Gitea Actions secret on sam/archipelago only if publish ever needs to run anywhere other than Gitea — it does not. Closing as resolved by the mirror change.
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 archipelago repo's GitHub mirror has only the ARCHIPELAGO_CATALOGUE_KEY Actions secret; DEPLOY_TOKEN is absent, so the publish workflow's
skopeo logingets an empty password and the run fails (run 41474436585, 2026-11-02). Earlier publishes logged into ghcr.io with a masked password, so the workflow moved to the Gitea registry without the mirror secret being migrated. Done when a publish run on main reaches the registry login step with a non-empty credential and publishes the signed catalogue.Root cause found: the failure email came from the GitHub mirror, which was running duplicate CI with no secrets. Gitea Actions is the real CI and already published successfully: publish run 1260 on 6f28cf9 (forge-gitea:1.2.0, forge-github:1.2.0, signed catalogue) is green on git.catlow.cloud. Actions are now disabled on the GitHub mirror (samcharles93/archipelago), so no runs or notification emails originate there. Remaining for Gitea-only operation: DEPLOY_TOKEN must exist as a Gitea Actions secret on sam/archipelago only if publish ever needs to run anywhere other than Gitea — it does not. Closing as resolved by the mirror change.
Duplicate of #1785 — same failure, filed 23 seconds later. Closing this one; tracking the fix there.