Skip to content

v0.6.0 — pull published images, don't build them

Choose a tag to compare

View all tags
@jozer-rami jozer-rami released this 07 Aug 06:32
· 199 commits to main since this release
v0.6.0
07bca5f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.6.0

Promotes the dev integration branch to main and out to production. 449 non-merge commits since v0.5.0 (265 fix · 68 test · 38 feat · 29 docs · 13 ci · 12 chore · 11 perf · 7 refactor).

Highlights

make minikube-setup no longer builds images. It pulls them from ghcr.io/evenfire-ai, published for both linux/amd64 and linux/arm64. An Apple Silicon machine gets a native image without compiling ~23 services. make minikube-setup-local (or IMAGE_SOURCE=local) restores the previous build-everything path.

Release images are promoted, never rebuilt. Tagging v* copies the exact digests already proven on dev into the release tag, so what ships is byte-identical to what was tested. The promotion refuses any image that is not multi-arch.

One image manifest, one release writer. deploy/images.json is now the single source for every image list, and the ghcr deploy pin is a checked release coordinate alongside the desktop version, so the images a cluster pulls and the version it reports can no longer drift apart.

MCP servers move to registry distribution. They are installed on demand from the evenfire registry instead of being loaded into the cluster at setup.

Registry and connector work. Self-hosted Marketplace UX redesign with an org area, zero-touch auto-claim on registration with explicit recovery, derived registry auth gating, credential rotation for existing MCP connectors, and self-provisioned image-pull credentials for recipe workloads.

Per-agent GFS delegation. User-plane backend plus desktop UI, with bulk subjects[] grants.

Platform hardening. Authoritative fleet and MCP client hardening in mcp-host, a prereqs gate on setup, all 21 LLM providers plumbed into secrets, and unified model catalog and discovery in the Control UI.

Upgrading a local cluster

A fresh clone needs nothing beyond make minikube-setup. An existing cluster keeps the tag it last acquired, so pass MINIKUBE_IMAGE_TAG=v0.6.0 once, or rebuild the cluster, to move it onto the release images.

If minikube fails to start, MINIKUBE_MEMORY=9216 — the default requests more than a stock Docker Desktop ceiling allows.

Assets 8
Loading