Automate GHCR environment publishing

This commit is contained in:
Thales Maciel 2026-03-08 18:30:11 -03:00
parent 6406f673c1
commit 89d0cb93bf
5 changed files with 78 additions and 1 deletions

View file

@ -18,6 +18,7 @@ This repository ships `pyro-mcp`, an MCP-compatible package for ephemeral VM lif
- The packaged runtime images under `src/pyro_mcp/runtime_bundle/` are stored in Git LFS.
- Use `make runtime-bundle` to regenerate the packaged runtime bundle from `runtime_sources/`.
- Use `make runtime-materialize` to build real runtime inputs into `build/runtime_sources/`.
- Use `make runtime-publish-official-environments-oci` after materialization to push the official OCI environments to their configured registry targets.
- Use `make runtime-fetch-binaries`, `make runtime-build-kernel-real`, and `make runtime-build-rootfs-real` if you need to debug the real-source pipeline step by step.
- Use `make runtime-boot-check` to run a direct Firecracker boot validation against the bundled runtime artifacts.
- Use `make runtime-network-check` to validate outbound internet access from inside the guest.
@ -30,6 +31,7 @@ This repository ships `pyro-mcp`, an MCP-compatible package for ephemeral VM lif
- After heavy runtime work, reclaim local space with `rm -rf build` and `git lfs prune`.
- The pre-migration `pre-lfs-*` tag is local backup material only; do not push it or it will keep the old giant blobs reachable.
- Public contract documentation lives in `docs/public-contract.md`.
- Official GHCR publication workflow lives in `.github/workflows/publish-environments.yml`.
## Quality Gates