Aller au contenu

v0.1.0-alpha.489

Released 2026-10-15.

Features

Change Signals

  • A table read where it lies (not replicated) that declares a probing change signal -- probe or ttl_probe, its own else its source's -- is a signal-only node of the event loop: its probe (MAX of its watermark column, a count, or its probe_query) runs on its cache TTL, and a change is posted to the materialized views that read it, which recompute and ripple on to theirs.
    • A live table that declares a probe is a signal-only node for its views
    • The quality demo, data you can trust, driven by landing alone

Triggers

  • A trigger says when something runs, and what runs is an ordinary command (python or statement), a SQL statement or a webhook.
    • A trigger fires on a table's change or event, and runs a command
    • A table floored by its own replicate builds its replica (#269); a write to a native-feed table fires its triggers from the feed alone
    • The admin Triggers page -- every automatic run in one place, read and edited in its panel

Changes

api-source

  • An API-backed table's date and timestamp columns are typed (#267)

auth

  • Rights follow the roles a request acts as, never every role held
  • Selecting an environment is judged by every role held, as it is decided before the acting roles exist

demo

  • Cap the reviews run-time stores' memory for the cloud node

demos

  • A bundle build lands a live account's tables with its key, and refuses an empty one
  • The insurance vertical demo -- property exposure against hazard risk
  • A tour's Polly questions are answered at the bundle build and stored
  • A scaffolded demo's example step opens on the GraphQL page
  • A scaffolded demo's example step opens the GraphQL page

deploy

  • The embedding-model hub cache on the host; a sonnets sandbox searches by meaning (CI)

duckdb

  • A MongoDB column named apart from its field is found (#266)

explorers

  • A demo visitor's OpenAPI page loads, and GraphQL reopens on its last tab

gcp-saas

  • The control-plane Postgres runs on the control-plane VM; Cloud SQL removed

governance

  • A star reads only the columns the role is served; RETURNING is governed

jdbc

  • Drop the connection mode setting, which had one value and changed nothing

mv

  • A view the event loop refreshes is marked fresh in the MV registry (#268)

replicas

  • Replica builds as ops tables, with a build log and failures per source and day

roles

  • A role's max_rows is set by the nearest role that declares it, as rate_limit is

row-level

  • A row-level table is read through ANY filter, fetched by that filter; DIRECT reads live

sandbox

  • cloud.provisa.dev offers weblogs, files, sonnets and reviews
  • A demo's own embedding models reach its sandboxes
  • A demo sandbox is deleted after an hour without use (was a day)

temp-tables

  • A session's temporary tables are bounded, and a gone session's are reaped

ui

  • js-yaml is a dependency of its own, so the live demos page check runs

writes

  • A source with no direct driver is written through the engine