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:50:42 +00:00
The publish now names the missing secret instead of logging in with an empty password: publish.yml checks DEPLOY_TOKEN before the skopeo login and fails with a named error, so an unconfigured mirror no longer reads as an unauthorized login (archipelago: ci(publish): name the missing DEPLOY_TOKEN instead of logging in with an empty password).
What is left is the configuration: the mirror still carries only ARCHIPELAGO_CATALOGUE_KEY. Set DEPLOY_TOKEN there (values stay CI-only) and re-run a publish on main; done when it gets past the login and pushes the signed catalogue.
The publish now names the missing secret instead of logging in with an empty password: `publish.yml` checks `DEPLOY_TOKEN` before the skopeo login and fails with a named error, so an unconfigured mirror no longer reads as an unauthorized login (archipelago: `ci(publish): name the missing DEPLOY_TOKEN instead of logging in with an empty password`).
What is left is the configuration: the mirror still carries only `ARCHIPELAGO_CATALOGUE_KEY`. Set `DEPLOY_TOKEN` there (values stay CI-only) and re-run a publish on main; done when it gets past the login and pushes the signed catalogue.
Obsolete: Actions is disabled on the GitHub mirror and archipelago publishes from Gitea. Publish run 1885 there logged in and published the signed catalogue.
Obsolete: Actions is disabled on the GitHub mirror and archipelago publishes from Gitea. Publish run 1885 there logged in and published the signed catalogue.
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.The publish now names the missing secret instead of logging in with an empty password:
publish.ymlchecksDEPLOY_TOKENbefore the skopeo login and fails with a named error, so an unconfigured mirror no longer reads as an unauthorized login (archipelago:ci(publish): name the missing DEPLOY_TOKEN instead of logging in with an empty password).What is left is the configuration: the mirror still carries only
ARCHIPELAGO_CATALOGUE_KEY. SetDEPLOY_TOKENthere (values stay CI-only) and re-run a publish on main; done when it gets past the login and pushes the signed catalogue.Obsolete: Actions is disabled on the GitHub mirror and archipelago publishes from Gitea. Publish run 1885 there logged in and published the signed catalogue.