This release includes 1 breaking change for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
ReleasePort's take
Light signalVersion v0.6.8 of SLayer rejects colons (:) in column, measure, model, datasource, and query names.
Why it matters: Update naming conventions before upgrading to v0.6.8; otherwise queries referencing old names will fail.
Summary
AI summaryColon (:) is now rejected in column, measure, model, datasource, and query names.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Every `slayer ingest` and `--ingest-on-startup` boot pass now re-embeds memories rooted at the ingested datasource. Every `slayer ingest` and `--ingest-on-startup` boot pass now re-embeds memories rooted at the ingested datasource. Source: llm_adapter@2026-05-21 Confidence: high |
— |
| Deprecation | Medium |
Colon (`:`) is now rejected in column, measure, model, datasource, and query names. Colon (`:`) is now rejected in column, measure, model, datasource, and query names. Source: llm_adapter@2026-05-21 Confidence: high |
— |
| Bugfix | Medium |
Stale `embeddings.db` created before credentials are available is automatically repaired by the next ingest. Stale `embeddings.db` created before credentials are available is automatically repaired by the next ingest. Source: llm_adapter@2026-05-21 Confidence: high |
— |
Full changelog
SLayer 0.6.8
A small follow-up release that keeps your memory embeddings in sync.
If you save memories and then change your data (or set up OPENAI_API_KEY after the fact), you no longer have to do anything special to get search working. Every slayer ingest, and every --ingest-on-startup boot pass, now re-embeds the memories rooted at the datasource being ingested. A stale embeddings.db (created before credentials were available, or after a hand-edit of memories.yaml) is repaired by the next ingest. If a particular memory fails to embed, the startup log attributes it as memory:<id> so you can tell it apart from a model or datasource-doc failure.
One small naming rule change worth flagging: : is now rejected in column, measure, model, datasource, and query names. The character is reserved for the aggregation suffix (revenue:sum) and was already implicitly off-limits; the validators now make that explicit. If you have an existing name with a colon in it, rename it before upgrading.
Breaking Changes
- Colon (:) rejected in column, measure, model, datasource, and query names; existing identifiers containing ':' must be renamed.
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.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.
- v0.5.1 RecallHit.match_count renamed to RecallHit.score across MCP, REST, CLI, and SlayerClient.
Beta — feedback welcome: [email protected]