Latest Versions
Release metadata checked 2026-11-15 (Asia/Shanghai). The generator version endpoint reports the versions its deployed templates currently select. Package registries can move ahead of that endpoint. A newer published runtime is not proof that the deployed generator already emits it or that the combination passed a clean consumer test.
The 2026-10-27 School consumer run
recorded 7/7 SQLite verification with explicit source qualification:
six published runtimes plus Go WORKSPACE PASS — RELEASE PENDING. Go's
selected public v0.3.1 failed compilation in that run because it lacked two
emitted internal-ID methods. The historical RELEASE PENDING qualification
applies to those recorded sources. The versions observed below require their
own consumer verification before any historical release gap can be closed.
| Component | Deployed generator selection | Newest independently observed release | Source |
|---|---|---|---|
| Generator Server | 20261111.203110 | — | Version endpoint |
| Java runtime | 1.556-RELEASE | 1.557-RELEASE | Version endpoint, Maven metadata |
| Rust runtime | 7.0.0 | 8.0.0 | Version endpoint, crates.io |
| Go runtime | v0.4.0 | v0.5.0 | Version endpoint, Git tag |
| Python runtime | 0.4.0 | 0.5.0 | Version endpoint, PyPI |
| .NET runtime | 0.4.0 | 0.5.0 | Version endpoint, NuGet 0.5.0 |
| TypeScript runtime | 0.4.0 | 0.5.0 | Version endpoint, npm |
| Swift runtime | 0.4.0 | 0.5.0 | Version endpoint, Git tag |
cargo-teaql | Not reported | 2.0.14 | crates.io |
| TeaQL Maven plugin | Not reported | 1.1.1 | Maven metadata |
The generator selections above have not changed. Java's published package also advanced during this check; its generator selection stays at 1.556-RELEASE. NuGet's official 0.5.0 metadata and the site CI observed .NET 0.5.0, while a local flat-container index still returned 0.4.0 and its 0.5.0 nuspec request returned 404. This publication/cache discrepancy is retained as an observation, not a successful installation claim.
Existing verified versions
Published, generator-selected and verified for a specific example are separate facts. This update checks release metadata only; it does not rerun consumer applications or certify the newly listed versions. The table below selects the existing Order first-flow baselines and records their scope. It is not an exhaustive list of all verified capabilities or a claim about the newest version that could pass.
| Runtime | Existing Order first-flow evidence | Scope and release boundary |
|---|---|---|
| Java | Published 1.555-RELEASE; 2026-11-14 first-run receipt. | Source-package build and SQLite seed/read/edit/readback. Later JDBC lifecycle/soak repairs remain RELEASE PENDING. |
| Rust | Published 5.0.7; 2026-11-14 first-run receipt. | Locked source-package build and SQLite first read/edit. Later workspace pagination/advanced Order remains WORKSPACE PASS — RELEASE PENDING. |
| Go | Exact workspace source in the 2026-10-27 first-flow receipt. | WORKSPACE PASS — RELEASE PENDING. The recorded public v0.3.1 compilation failure is retained; a newer tag alone does not close that gap. |
| Python | Published 0.3.1; 2026-10-27 first-flow receipt. | Original eight-case native SQLite flow. Later workspace pagination/advanced Order remains WORKSPACE PASS — RELEASE PENDING. |
| .NET | Published 0.3.1; 2026-10-27 first-flow receipt. | Original eight-case native SQLite flow. Later workspace condition-key/pagination/advanced Order remains WORKSPACE PASS — RELEASE PENDING. |
| TypeScript | Published 0.3.1; 2026-11-15 first-run receipt. | Locked npm build and Node SQLite first read/edit. Later deletion-readback/pagination/advanced Order remains WORKSPACE PASS — RELEASE PENDING; nullable generator repair remains pending generator deployment. |
| Swift | Published 0.3.1; 2026-10-27 first-flow receipt. | Original eight-case native SQLite flow. Later retained-ID invalidation includes an application-owned adapter; this is not an Apple UI or new-release qualification. |
The later seventeen-case Order receipt and School advanced evidence keep their own source identities, failures and qualifications. No runtime RELEASE PENDING or generator-deployment marker is cleared by updating this page. A release gap can be closed only by a new, source-bound receipt for the relevant model, provider and scenario using the released package.
Selecting a dependency
Use the version emitted by your generated workspace for its default dependency set. To test a newer released runtime, use a supported model-level version override where one exists, regenerate into a separate workspace, and run the owning runtime example and clean consumer tests. Python and .NET do not yet have a canonical KSML version override; use a separate consumer workspace for those experiments. Do not assume that a tag, package, or endpoint row alone proves compatibility.
Current commands
cargo install cargo-teaql --version 2.0.14 --locked
cargo teaql --version
cargo teaql services
cargo teaql evaluate --input models/
cargo teaql rust-lib-core --input models/ --output generated/rust-lib-core
The Maven plugin uses one dynamic generate goal and a live target catalog:
mvn io.teaql:teaql-maven-plugin:1.1.1:list-services
mvn io.teaql:teaql-maven-plugin:1.1.1:generate -Dinput=models -Dservice=java-lib-core
The endpoint reports component selections, not a supported combination matrix. Read the current capability and evidence guide and the dated database matrix before treating a runtime/provider combination as verified. Historical release material remains in the Changelog.
The site CI checks version drift with npm run check:latest-versions. It reads
the generator endpoint, Java and plugin Maven metadata, Rust and CLI Cargo
indexes, npm, PyPI, the NuGet published-package feed, and the Go and Swift GitHub
tag feeds. The NuGet check uses its explicit latest stable entry rather than a
possibly lagging regional download index. Registry
discovery still proves only that a release exists; it does not promote that
release to a verified combination.