CI: runs-on docker for the publish workflow #16
Loading…
Reference in a new issue
No description provided.
Delete branch "heimdall/workflow-runs-on-docker"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One line in
.github/workflows/publish-container.yml:runs-on: ubuntu-latestbecomesruns-on: docker, the label the forge runners carry. Nothing else in CI changes.Evidence: Bifrost's runs on the forge are mostly
cancelled(ids 22-245); the two that started (540, 668) failed.Caution: the job logs in to ghcr.io with
secrets.GITHUB_TOKENand pushes the image. On the forge that token is not a GHCR credential, so expect the login step to fail on a push to main until the publish target is decided. The workflow runs only on push to main,v*tags and manual dispatch, so this PR itself triggers no run.Not merged; merge waits on a reviewer.
Closing unmerged. Eureka ruled in #minds on 2026-11-09 to drop the publish job: Bifrost goes live as a release directory under /srv/bifrost/app/releases switched by Idunn with a rollback point, nothing on this estate pulls a container image, and the job would fail on every push to main (ghcr.io with the forge's GITHUB_TOKEN) for a registry nobody reads. The workflow is deleted in a separate PR instead.
Pull request closed