Skip to content

0.7.0b3 — semlayer demo, and the no-Python path actually works

Pre-release
Pre-release

Choose a tag to compare

@raj-devnath raj-devnath released this 13 Nov 07:43
· 32 commits to main since this release
52d8c6a

semlayer demo: a warehouse for people who do not have one

The first thing a new user needs is something to point infer at, and "find
a warehouse first" is a wall in front of the only thing that would show them
what this does. semlayer demo writes one: thirty-six tables with cryptic
names, no declared primary or foreign keys anywhere in the DDL, an SCD2
customer dimension, two aggregate tables that reconcile with their facts only
under a filter nobody wrote down, and two deprecated legacy tables.

A clean tutorial schema would prove nothing. The claim semlayer makes is
about warehouses where the keys are undeclared and the rules are unwritten,
so the thing handed to a new user has to be one of those. Everything the
engine finds in it, it finds without help from the catalog.

The generator moved out of fixtures/ into the package to make this
possible: a person who installed from PyPI has no copy of the repository,
which is exactly the person who needs a warehouse to try.

The documented "with nothing installed" path did not work

docs/mcp.md and llms-install.md told users to run

uvx --with "semlayer[warehouses]" semlayer mcp

On a machine with no Python that fails. With no Python present uv
downloads the newest CPython -- 3.15 today -- and duckdb publishes wheels
only to cp314, so the install falls back to building from source, wants
CMake, and dies after about two and a half minutes. requires-python = ">=3.10" has no upper bound, so uv considered 3.15 fair game.

Every uvx invocation in the docs now pins --python 3.13. Reproduced and
fixed against a sandbox holding only a shell, curl and coreutils, where the
whole path now works: uv installs in 4.7s, semlayer demo writes the
warehouse, infer --no-llm produces a valid layer over 36 tables, and lint
catches both the fan-out and the required filter. Cached calls take 0.28s.

Raise or drop the pin once every dependency ships wheels for the Python uv
would otherwise pick.

A VS Code and Cursor extension

Lives in extension/. It carries no engine and speaks no MCP: it runs
semlayer <command> --json and renders the result, so the editor cannot
disagree with the terminal. SQL diagnostics as you type, the review queue as
a two-pane screen, drift, inference settings, and one click to write an MCP
client's config.

See docs/vscode.md.

llms-install.md, and an icon on the registry entry

Agent-driven installers read README.md and llms-install.md and nothing
else. The MCP configuration lived in docs/mcp.md, one link away, so an
agent asked to set semlayer up had to guess at it. llms-install.md now
carries the config block inline, along with the three things such an agent
otherwise gets wrong: that --with semlayer[warehouses] is load-bearing
rather than decorative, that no API key is required so setup must not block
on one, and that status is how you verify the install.

The missing extra is worth naming because of how it fails. Without the
warehouse drivers the server starts cleanly and finds a warehouse it
cannot open, so the configuration looks correct until the first real
request.

server.json gains icons, pointing at the mark now served from
semlayer.dev. Clients and directories render it; an entry without one looks
abandoned beside entries that have one.

A container image, and the version clients were shown was the SDK's

Dockerfile and .dockerignore land in the repository. The image runs the
MCP server over stdio as an unprivileged user, carries the warehouses
extra so a first connection can actually reach a warehouse, and is built
from the source tree so it matches the commit rather than the last release.
ENTRYPOINT is the binary and CMD is the subcommand, so docker run ... infer works without --entrypoint.

-i is not optional when running it: the MCP stdio transport IS the
container's stdin and stdout, and without it the server reads EOF and exits.

The ignore file is an allowlist rather than a blocklist, which is not
stylistic: the repository is about 5 GB, 4.5 GB of that fixtures, and the
wheel needs 2.6 MB of it. Every build would otherwise stream all of it to
the daemon. A build-time dependency added later has to be added there too.

Found while writing the image's smoke test: every client was being told
serverInfo.version: 1.28.1, which is the version of the mcp SDK, not of
semlayer.
FastMCP does not forward a version to the low-level server, and
the SDK falls back to its own package version when that is None. Clients
display it, and bug reports quote it, so the number people have been
reporting was never ours. It now reports the real version, and the
handshake also carries websiteUrl.

Releases register themselves with the MCP Registry

server.json now lives in the repository, and release.yml publishes it to
the official MCP Registry after the PyPI upload. It has to run in that order:
the registry checks that the named package exists at the named version on
PyPI and that its published description carries the mcp-name marker, and
neither is true until the upload succeeds.

Both version fields in server.json are written from pyproject.toml at
publish time rather than from the git tag, because the tag says
v0.7.0-beta.2 and the package says 0.7.0b2 -- it is PyPI the registry
checks against, so PyPI is what the file is pinned to. The committed copy
cannot drift from a release as a result.

Registry versions are immutable, so re-running a successful release reports a
duplicate version. That one error is treated as success -- the listing
already describes the release -- and every other failure fails the job
loudly rather than continue-on-error, which is how the benchmark gate
rotted across two releases.