Since ~2026-08-08, every hyperpolymath/oikosbot@v0.1.0 consumer fails at:
IMAGE: ghcr.io/hyperpolymath/oikos:latest
docker: Error response from daemon: Head "https://ghcr.io/v2/hyperpolymath/oikos/manifests/latest": denied
Observed red on metadatastician/enaction-engine (main, since 08-09) and metadatastician/idaptik-ums (PR + main boards, 08-10). It was green on idaptik-ums main on 08-06, so the package/registry state changed between 08-06 and 08-09 — most likely package visibility or a deleted :latest tag.
Two asks:
- Make the
oikos container package publicly pullable again (package settings → public), or restore/repoint :latest.
- Cut release v0.1.1:
action.yml on main already defaults to the digest-pinned ghcr.io/hyperpolymath/oikos@sha256:24598b73…, but the only release (v0.1.0, 2026-07-28) still defaults to :latest. A tagged release carrying the digest default makes consumers immune to tag drift.
Consumer-side interim (once the package is public): with: image: ghcr.io/hyperpolymath/oikos@sha256:24598b73… works at v0.1.0 since the image input exists there. Related consumer fix: metadatastician/enaction-engine#43 removes the if: always() that was masking this root cause behind a phantom results.sarif error.
Since ~2026-08-08, every
hyperpolymath/oikosbot@v0.1.0consumer fails at:Observed red on metadatastician/enaction-engine (main, since 08-09) and metadatastician/idaptik-ums (PR + main boards, 08-10). It was green on idaptik-ums main on 08-06, so the package/registry state changed between 08-06 and 08-09 — most likely package visibility or a deleted
:latesttag.Two asks:
oikoscontainer package publicly pullable again (package settings → public), or restore/repoint:latest.action.ymlon main already defaults to the digest-pinnedghcr.io/hyperpolymath/oikos@sha256:24598b73…, but the only release (v0.1.0, 2026-07-28) still defaults to:latest. A tagged release carrying the digest default makes consumers immune to tag drift.Consumer-side interim (once the package is public):
with: image: ghcr.io/hyperpolymath/oikos@sha256:24598b73…works at v0.1.0 since theimageinput exists there. Related consumer fix: metadatastician/enaction-engine#43 removes theif: always()that was masking this root cause behind a phantomresults.sariferror.