Skip to content

SparkGLM 0.1.0 — tool boundaries and product versions

Latest

Choose a tag to compare

@data-angel data-angel released this 22 Oct 15:57
68b71e0

SparkGLM 0.1.0 introduces semantic product versions and fixes GLM tool boundaries.

Fixes short-prose tool suppression and literal tool-XML handling in GLM. Quoted tags and fenced examples remain text; real tool calls retain constrained arguments. Streaming preserves adjacent text and whitespace.

Includes SparkGLM #57, #58, #59 and #60, with engine fixes in Atlas #7 and #8. Issue #55 is closed.

The final engine source passed 32/32 XML controls across OpenAI/Anthropic and blocking/streaming, 15/15 short ToolEvalBench scenarios, and 2,890 native server tests. The earlier loop-only revision passed the 60-case context-pressure sweep. These are correctness checks, not performance claims. Broad Atlas CI retains documented pre-existing failures.

The attached image pin manifest identifies the immutable registry digest, product revision, install tree, engine and checkpoint revisions. Deployment and published-image verification are recorded separately in the release receipt. The managed rollout covers the existing TP2 GLM lane on Sparks 01/02.

Run ./start.sh --version for the checkout version and exact Atlas pin. ./start.sh status also shows the product version and image ID on both running ranks. Images expose the same version with docker run --rm IMAGE --version, in startup logs and in the OCI version label. Install-tree hash tags remain reproducible. See versioning policy.

Build limitation: the canonical image checks passed all test stages, then failed in the existing workspace Clippy gate (a spark-comm test import and two spark-model lints). The release uses the supported runtime-only build path after those checks and the native source qualification above; the full workspace lint gate is not green.

Published-image rollout verification: both managed TP2 ranks run version 0.1.0 from the attached immutable digest. All 32/32 gateway XML/tool checks passed; health, model advertisement and restored routes were verified. The previous image and prefix cache are retained for rollback.