Latest Versions

The authoritative source for the current TeaQL component baseline is:

TeaQL latest-version endpoint

Last checked: 2026-09-06.

Component	Latest version	Use
Generator Server	20260906.092036	Model evaluation and generation service baseline.
teaql-java	1.546-RELEASE	Current Java runtime and integration artifact baseline.
teaql-rs	4.3.3	Current Rust runtime workspace baseline.
teaql-golang	v0.1.4	Current Go runtime baseline.
teaql-python	0.1.2	Current Python runtime baseline.
teaql-dotnet	0.1.2	Current .NET runtime baseline.
teaql-ts	0.1.9	Current TypeScript runtime baseline.
teaql-swift	0.1.3	Current Swift Package Manager tag; not yet returned by the version endpoint.
cargo-teaql	2.0.13	Current Rust generator client baseline.

Client Tool Baseline

Client artifact versions are not returned by the latest-version endpoint. They must be verified from their official source and installed help output.

Client	Verified current version	Evidence
TeaQL Maven plugin	1.1.1	Built and installed from the official Maven plugin repository; generated plugin help exposes eval, generate, list-services, ping, show-config, and help.
Cargo client	2.0.13	Latest crates.io release metadata and the maintained client-version check. The complete end-to-end run remains dated evidence and is not silently re-attributed to this release.

The Maven plugin 1.1.1 artifact is the current published baseline. The retained 2026-07-13 list-services run is behavioral evidence for dynamic generation targets, not proof that every current target was rerun on that date. Query the catalog immediately before selecting -Dservice=<target>.

How to Use This Table

• Use teaql-java 1.546-RELEASE in current Java dependency examples.
• Use teaql-rs 4.3.3 as the current Rust runtime baseline.
• Treat Generator Server 20260906.092036 as the generation-service version behind the current workflow.
• Use dependency versions emitted by the current generator for component artifacts not listed by the endpoint.
• Check installed Cargo and Maven client help for client-specific flags and goals; the endpoint does not currently return those client artifact versions.

Latest Does Not Mean Every Combination Is Supported

The endpoint reports current component versions. It does not, by itself, prove every framework, provider, database, driver, or toolchain combination.

Before production adoption:

1. Check the Compatibility Matrix.
2. Generate from an unchanged model.
3. Review the generated dependency and API diff.
4. Build and test the selected Java/Rust/provider combination.
5. Record rollback and migration evidence.

For dated current observations and historical release material, see the Changelog.

Automated Drift Check

The documentation CI checks the TeaQL version endpoint, crates.io sparse index, and TeaQL Maven repository metadata:

npm run check:latest-versions

The check fails when maintained baseline pages omit the latest server, runtime, Cargo client, or Maven plugin release. It also scans operational content under docs/ and src/ for stale cargo-teaql install commands, fully qualified Maven plugin commands, TeaQL Java dependency blocks, and direct TeaQL Rust dependency pins. Blog posts remain historical records and are not rewritten by this check.