Repository navigation
0.7.0b8 — the Action can be listed, and the engine runs in a browser tab
Pre-release
Pre-release
uv tool install semlayer==0.7.0b8
The Action is named semlayer SQL check, so it can be listed
The GitHub Marketplace refuses an Action whose name matches an existing user
or organisation, and semlayer is one. The name: in action.yml is now
semlayer SQL check. That is the listing title only. A workflow refers to
the repository, so nothing that uses the Action changes:
- uses: semlayer-dev/semlayer@v0.7.0-beta.8
with:
mode: lint # or drift, to fail when the warehouse moved
layer: layer.yamlThe engine runs where there are no threads, and says what it is doing
Three changes made for running the engine inside a browser tab on Pyodide,
which is what https://try.semlayer.dev does. A native run behaves as before.
- The package imports and infers without
mcpinstalled. Only
build_serverneeds it. - A query watchdog that cannot start its timer runs the query without one
and records that, andrun_sqlno longer reports a time limit it could
not arm. - Progress events carry more: Profile names the table it is on, Link emits
afoundevent listing the relationships before it finishes, and Enrich
reports five steps where it reported none. A consumer that switches on
the event kind must ignore kinds it does not know.