This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryDimension-only queries can opt-out of deduplication and SQLite ingestion now auto-widens integer columns that store floats or mixed text.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Low |
Adds opt-out of deduplication for dimension-only queries via distinct_dimension_values flag. Adds opt-out of deduplication for dimension-only queries via distinct_dimension_values flag. Source: llm_adapter@2026-06-09 Confidence: high |
— |
| Bugfix | Medium |
Fixes SQLite ingestion type mismatches by auto-widening integer columns that store floats or mixed text. Fixes SQLite ingestion type mismatches by auto-widening integer columns that store floats or mixed text. Source: llm_adapter@2026-06-09 Confidence: high |
— |
Full changelog
0.7.2
Two small wins for SQLite users and anyone needing raw rows.
Dimension-only queries now have an opt-out for deduplication. Set distinct_dimension_values: false on your query to get raw rows back instead of the default GROUP BY over all dimensions. Useful when you want every row, duplicates included. Available on the SlayerQuery field, MCP query / query_nested, REST POST /query, and the Python client.
If you use SQLite, ingestion now checks what your columns actually store instead of trusting the declared type. Columns declared INTEGER that actually hold floats or mixed text are widened automatically, so aggregates like AVG no longer silently truncate to wrong values. Re-run slayer ingest (or slayer storage migrate-types for already-saved models) to pick up the fix.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Track SLayer, a semantic layer maintained by your agent
Get notified when new releases ship.
Sign up freeAbout SLayer, a semantic layer maintained by your agent
All releases →Related context
Related tools
Earlier breaking changes
- v0.7.1 Changes `search()` response to a single flat `results` list capped by `max_results`, removing separate `memories`, `example_queries`, and `entities` buckets.
- v0.7.1 Changes `search()` to return a single flat `results` list, removing per‑bucket caps.
- v0.6.3 Datasource names now reject dots, slashes, nulls, empty/whitespace; existing names containing '.' will fail validation on upgrade.
- v0.6.0 recall_memories surface entirely removed with no deprecation shim.
- v0.5.1 Two-mode reference semantics enforced: SQL mode accepts arbitrary SQL; DSL mode strictly resolves identifiers.
Beta — feedback welcome: [email protected]