This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
ReleasePort's take
Light signalVersion v0.6.7 introduces multi-stage queries via the REST API and per-bucket ranking invariance for search().
Why it matters: Test multi-stage query support in development environments before deploying v0.6.7.
Summary
AI summaryMulti-stage queries added to the REST API.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Per-bucket ranking invariance added to search() Per-bucket ranking invariance added to search() Source: llm_adapter@2026-05-21 Confidence: high |
— |
| Feature | Medium |
Multi-stage queries supported via REST API Multi-stage queries supported via REST API Source: llm_adapter@2026-05-21 Confidence: high |
— |
Full changelog
What's Changed in v0.6.7
- Per-bucket ranking invariance in search(), by @ZmeiGorynych in https://github.com/MotleyAI/slayer/pull/127
- Multi-stage queries in REST API, by @AivanF in https://github.com/MotleyAI/slayer/pull/126
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]