StackKits v0.15.0
·
44 commits
to main
since this release
Added
- Cloud Kit now resolves a required provider-neutral Cloud core workload for
base,auth,id, andcoolify, renders one digest-pinned Compose
project, and executes it through a closed local runtime owner on an
externally supplied host. - Owner-signed Cloud runtime custody stores only service-scoped PocketID,
TinyAuth, and Coolify material. Provider credentials, server credentials,
leases, inventory, and provider lifecycle remain outside StackKits. - Cloud Apply and Verify bind the exact generated artifact, authenticated
execution channel, nine-service image graph, and five post-apply health
conditions. The generated access manifest exposes the four Cloud core
services over the plan-owned public TLS domain.
Changed
- Cloud Kit's native default generation target is Compose and
cloud-coreis
a required workload. IONOS, centron, BYO-VPS, and local-host selection remain
Techstack concerns; StackKits receives only an enrolled host channel.
Full Changelog: v0.14.28...v0.15.0