-
v0.8.0 Stable
released this
2026-09-19 16:09:30 +00:00 | 0 commits to main since this releaseVSKI v0.8.0
vcli: the vski CLI ships as a release asset
The
vski-clirepo (submodule of platform since this release) builds
vcliand attaches it to every release from now on:curl -fsSL https://vski.sh/x/platform/releases/download/latest/vcli -o vcli chmod +x vcliTwo halves:
-
Model packs (
info/verify/inspect/import, the
pkg/pack+pkg/npyGo libraries) — unchanged tooling for the
vski.model/2opaque pack format. -
VSKI LAB management (new):
vcli lab initscaffolds a self-hosted
lab — it downloads the lab compose from the app deploy (keeping the
stack definition fresh independently of vcli releases), resolves the
api/jupyter base images to exact registry digests, and renders the lab
layout:data/ the platform's own data (multi-tenant SQLite) projects/ project data — the api's bind docker/ api + jupyter image shims (FROM the registry images) — the place to add local dependencies (GPU/rocm userland, …) .env user-editable environmentBecause the api/jupyter images BUILD from the local shims, a lab can
grow its own dependencies without forking the stack; host-side
additions (device passthrough) go in adocker-compose.override.yml.Also:
vcli lab update(refresh compose + pins, fill missing.env
keys, never touching your edited shims),vcli lab up|down|status,
andvcli lab migrate(split a pre-vclicache/datalab into
data/+projects/, dry run by default).
The release pipeline (
release.ts) initializes the submodule, stamps the
version in (vcli version), and uploads the binary alongsidevskiand
vski-standalone.Compatibility
No engine, API or storage changes — v0.8.0 adds the
vski-clisubmodule
and the release-asset pipeline. Existing standalone binaries and images
are unaffected. Thelatest/vclidownload URL goes live with this
release; the lab compose itself is served by the app deploy
(/docker-compose.lab.yml).Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-