What's New¶

The highlights of what's shipped recently, newest first. For the operator-grade release notes that self-hosters should read before upgrading (breaking changes, migrations, required actions), see GitHub Releases.

June 2026¶

The Tabular validator got its authoring UI. Define a column schema (types, ranges, patterns, uniqueness) in a dedicated workspace and add row rules — CEL expressions over row.* for cross-column logic like row.min_depth <= row.max_depth. See the Tabular validator guide.

Every validator now sees the submission envelope. The new submission.* CEL namespace exposes submitter metadata (submission.metadata.<key>, submission.short_description) and server-stamped facts (submission.file_type, submission.size, submission.uploaded_at) to assertions — for any file format, even when the payload isn't JSON. Details in CEL expressions.

The CLI learned to carry metadata. validibot validate gained repeatable --meta key=value flags and --short-description, which flow straight into the submission.* namespace for rules to read (CLI 0.3.0). The 0.3.1 release hardened the CLI's output rendering and credential store.

SHACL validation moved into an isolated container. Untrusted RDF parsing and author-supplied SPARQL now run in a sandboxed backend instead of the application process — same results, much smaller blast radius.

Assertion authoring got friendlier. CEL errors that used to fail silently at authoring time are now surfaced in the editor, and the results UI was refreshed.

Workflows travel. Export a workflow as a .vaf archive and import it into another deployment — see Import & export workflows.

May 2026¶

Tabular (CSV) validation arrived. Native column checks plus row-stage CEL validation landed as a new built-in validator.

Step inputs, step outputs, and a clearer vocabulary. The i.* namespace exposes what a validator can see at the start of a step, o.* what it produced, and "Copy to Signal" promotion now works for shared (validator-owned) catalog entries too — including EnergyPlus outputs.

Validator versions became plain integers. Workflow steps pin to an exact validator version (2, not v2.1.0-beta), which keeps old runs reproducible and makes version comparisons unambiguous.