Skip to content

Foretoken 0.0.7

Latest
Latest

Choose a tag to compare

View all tags
@shiweijiezero shiweijiezero released this 24 Oct 08:16
v0.0.7
92b1e01

What's changed

Reuse node images during source development

  • Source builds avoid downloading the full runtime again when its layers are already present on the node. Missing content is fetched automatically.
  • Automatic GitHub and Go download-source selection no longer triggers native Mooncake recompilation. Release builds and source deployments share the same cached native build inputs.
  • The Quick Start installs the published CLI and platform by default; code changes and parallel experiments use the source deployment workflow.

Preserve startup budgets through workload recovery

  • Availability observations now identify the Deployment or LeaderWorkerSet they belong to. A replacement workload waits for its own first model container before starting its budget; Pods retiring from an older workload no longer affect that clock.
  • The current workload keeps one unavailable interval across container restarts and member replacement. Recreating the workload starts a separate interval even if the preceding workload never became available.

Artifacts

This release provides foretoken==0.0.7 on PyPI, Helm Chart 0.0.7, the application archive attached below, and Linux amd64 control-plane, frontend and NVIDIA model-server environments with matching source-build caches. The inference runtime remains vLLM 0.31 with the complete Mooncake package. The MetaX runtime image remains deferred; source deployment is available.

Upgrading

Upgrade the CLI in its active environment:

uv pip install --upgrade foretoken==0.0.7  # Or: pip install --upgrade foretoken==0.0.7

The platform administrator runs foretoken install with the existing registry and custom values options, then redeploys the instances that should adopt the new controller. The platform upgrade adds ModelGroup.status.observedWorkloadUID. Previously unavailable Groups receive one fresh startup window when they first adopt workload identity; subsequent recovery retains the recorded window.

For source installations, select this release in a clean checkout, then update the platform:

git fetch origin tag v0.0.7
git switch --detach v0.0.7
foretoken install -e .

Redeploy with foretoken deploy PATH --name INSTANCE -e ., using the instance's existing Kustomize directory and name. Retain any registry and custom values options used by the installation.

Thanks

  • @shiweijiezero — native content reuse, workload-recovery fixes and end-to-end validation.

Full changelog

Changes from v0.0.6 to v0.0.7

Assets 6
Loading