Skip to content

This release adds 2 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

semantic-layer

Summary

AI summary

SLayer now exposes a Postgres wire‑protocol server on port 5145 enabling direct querying of semantic models from BI tools.

Changes in this release

Feature Medium

Adds Postgres wire protocol support via `slayer pg-serve` on port 5145.

Adds Postgres wire protocol support via `slayer pg-serve` on port 5145.

Source: llm_adapter@2026-05-31

Confidence: high

Feature Low

Enhances `search` by entity reference to include the referenced entity itself.

Enhances `search` by entity reference to include the referenced entity itself.

Source: llm_adapter@2026-05-31

Confidence: high

Full changelog

SLayer 0.7.0

You can now point Postgres-aware BI tools - Metabase, Superset, Tableau, Power BI, Looker - straight at SLayer. slayer pg-serve speaks the Postgres wire protocol on port 5145, so any client with a Postgres connector can query your semantic models with no shim or custom driver: the connection's database parameter picks a SLayer datasource, your models surface under public, and pg_catalog / information_schema introspection just works. It joins the Flight SQL facade (port 5144, slayer flight-serve) shipped in 0.6.10, which is wire-compatible with the upstream Apache flight-sql-jdbc-driver and the same JAR the dbt Semantic Layer connectors use. Together they make SLayer reachable from most of the BI ecosystem.

Other changes

  • search by entity reference now also includes the entity itself. Passing entities=["mydb.orders.amount"] and setting num_memories=0 and num_queries=0 returns just the entity, ditto for entities=["memory:42"]. Hidden models/columns and refs outside the requested datasource drop with a warning.

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 free

About SLayer, a semantic layer maintained by your agent

All releases →

Related context

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]