Latest Versions
Checked 2026-09-28. 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.
| Component | Deployed generator selection | Newest independently observed release | Source |
|---|---|---|---|
| Generator Server | 20260920.031540 | — | Version endpoint |
| Java runtime | 1.548-RELEASE | 1.551-RELEASE | Version endpoint, Maven metadata |
| Rust runtime | 5.0.2 | 5.0.3 | Version endpoint, crates.io |
| Go runtime | v0.2.4 | v0.2.7 | Version endpoint, Git tag |
| Python runtime | 0.2.4 | 0.2.7 | Version endpoint, PyPI |
| .NET runtime | 0.2.5 | 0.2.7 | Version endpoint, NuGet |
| TypeScript runtime | 0.2.4 | 0.2.8 | Version endpoint, npm |
| Swift runtime | 0.2.4 | 0.2.7 | Version endpoint, Git tag |
cargo-teaql | Not reported | 2.0.14 | crates.io |
| TeaQL Maven plugin | Not reported | 1.1.1 | Maven metadata |
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, NuGet, and the Go and Swift GitHub tag feeds. Registry
discovery still proves only that a release exists; it does not promote that
release to a verified combination.