mirror of
https://github.com/luxfi/help.git
synced 2026-09-24 00:24:29 +00:00
zeekayandHanzo Dev
260abb43ba
publish.yml asked for `runs-on: ubuntu-latest`. The git-runner behind
git.hanzo.ai advertises ~28 labels and that is not one of them, so the job was
never picked up here — it is one of 44 jobs sitting in `waiting` for exactly
that label. On GitHub it was equally stuck, because the luxfi org has zero
registered runners. Addressed to a runner that exists in neither place, it was
not a build; it was a queue entry.
Also removed, both GitHub-only assumptions:
- ghcr login via github.actor + secrets.GITHUB_TOKEN. On this forge
GITHUB_TOKEN is minted by git.hanzo.ai and ghcr.io answers `denied: denied`.
GHCR_USER/GHCR_TOKEN are luxfi org-level secrets here.
- cache-from/to: type=gha, which addresses the GitHub Actions cache service.
The v1.x.x bump is untouched: feat/BREAKING/type! to minor, else patch, never
a major. What changes is that the tag push now goes to github.com rather than
to the forge — this repo is a pull-mirror here and refuses receive-pack, so the
old `|| echo "tag push skipped"` had been silently tagging nothing.
Adds the checks node's release.yml learned the hard way: smoke the image before
it is allowed to exist at the registry, prove the pushed manifest resolves, and
stamp revision/ref/source labels. The smoke checks what a static-server image
cannot check itself — index.html exists and every asset it references is really
in the layer — so a hollow build cannot serve a white page with a 200.
Co-authored-by: Hanzo Dev <[email protected]>