Changelog

This page is the maintained version index for TeaQL documentation. It separates the current verified component baseline from historical narrative material.

The date on a baseline entry is its verification date unless an authoritative artifact publication date is explicitly cited. It must not be reinterpreted as the release date of every component in the row.

2026-09-06 — Current Verified Baseline

The official endpoint reports the generator and six independently versioned runtimes below. Swift is currently tracked by generated-source and runtime commit evidence rather than a version returned by the endpoint.

Component	Current version	Version authority	Maintained evidence
Generator Server	20260906.092036	Official latest-version endpoint	Current published generation-service baseline.
teaql-java	1.546-RELEASE	Latest-version endpoint and TeaQL Maven repository	Current published baseline.
teaql-rs	4.3.3	Latest-version endpoint and published crate set	Current published baseline.
teaql-golang	v0.1.4	Latest-version endpoint and Go module proxy	Current published baseline.
teaql-python	0.1.2	Latest-version endpoint	Current generator baseline.
teaql-dotnet	0.1.2	Latest-version endpoint	Current generator baseline.
teaql-ts	0.1.9	Latest-version endpoint and npm	Current published baseline.
teaql-swift	0.1.3	Git tag and Swift Package Manager resolution	Current typed SmartList baseline.
TeaQL Maven plugin	1.1.1	Plugin Maven metadata	Installed help/source, live target catalog, evaluation, generation, and regeneration.
cargo-teaql	2.0.13	crates.io package	Current published Rust generator client baseline.

Run npm run check:latest-versions to compare this baseline with the official server, Maven, and crates.io sources.

Current Observed Behavior

These are current-version observations and migration boundaries. Unless the source explicitly says so, they are not claims that a behavior was first introduced by the exact artifact version in the table.

• The retained Cargo 2.0.8 execution evidence uses evaluate; generation targets such as rust-lib-core and rust-app-console are invoked directly after querying services. The published 2.0.13 version is tracked separately and must not inherit that execution evidence without a rerun.
• Maven plugin 1.1.1 uses list-services and one dynamic generate goal with -Dservice=<target>; target names are obtained from the live catalog.
• Current handwritten queries end with comment → purpose → executeForXxx/execute_for_xxx; purpose is immediately before execution.
• Current entity persistence carries a concrete auditAs/audit_as before save or update.
• Rust generated workspaces use the narrower teaql-provider-postgres, teaql-provider-mysql, and teaql-provider-sqlite architecture rather than the historical SQLx-centered provider names.
• The recorded Rust SQLite combination generated, tested, started, queried, mutated with audit intent, and regenerated successfully.
• Java evaluation, java-lib-core generation, and regeneration succeeded, but the current generated workspace is not a runnable release baseline.

Known Limitations

• Swift does not yet expose a separately versioned package in the latest-version endpoint.
• No formal LTS, maintenance-duration, security-backport, or end-of-life policy has been published.

Use Migration Notes, Compatibility Matrix, and Verification Evidence before adopting this baseline.

Historical Published Material

These entries preserve the site's release and architecture chronology. They are not automatically compatible with the current baseline.

Publication date	Material	Recorded subject	Current treatment
2026-07-02	Why TeaQL Rust Removed SQLx	Move from SQLx-centered providers to narrower TeaQL provider contracts.	Current architecture direction; regenerate and use current crate names/versions. Code terminals in historical prose may not satisfy the current intent order.
2026-06-16	Spring Boot 4.1 and Java 21	Generated Java target using Java 21 and Spring Boot 4.1.0.	Observed again in current java-lib-core output, but not proof of every Java module/framework combination or a clean build.
2026-06-10	Java Runtime Modular Refactor	JPMS, non-Spring direction, audit/policy alignment, and module boundaries.	Architecture narrative; current public interfaces must be taken from the current runtime and generated output, not copied from the post.
2026-05-30	TeaQL 1.0.0 Release Notes	Umbrella Rust/Java API, audit, query-prefix, transaction, and agent-workflow changes.	Historical migration material. Its component coordinates, provider names, and command/version advice are not the current baseline.
2026-05-01	TeaQL Rust v0.7.0	Aggregation cache, debug logging, query expressions, and the then-current provider layout.	Historical only; listed SQLx/rusqlite provider crate names are obsolete for current generated workspaces.

Component History Gaps

The official repositories and artifact channels do not currently provide one complete, aligned set of release notes and publication dates for Generator Server 20260819.064259, teaql-java 1.529-RELEASE, teaql-rs 4.2.13, Maven plugin 1.1.1, and cargo-teaql 2.0.13.

Repository tags also use version lines that do not map cleanly to the current published artifact versions. Consequently, this changelog does not infer release dates, commit ranges, or “introduced in” claims from tag names.

To close the gap, each component release should publish a tag or immutable artifact-to-commit mapping and a release note using the structure below.

Required Shape for New Entries

Every new entry must include:

1. component and exact version;
2. publication date and immutable source/tag/artifact link;
3. added, changed, deprecated, removed, and fixed behavior;
4. generated API and dependency impact;
5. configuration/environment impact;
6. provider/schema/transaction impact;
7. security, audit, tenancy, and masking impact;
8. migration and rollback instructions;
9. exact verification commands, expected result, and evidence artifact;
10. known limitations and support status.

Do not publish an empty category as “none” unless the component owner reviewed that category. Unknown information should remain explicitly unknown.