0.1
Every published okengine release, newest first.
all series · 0.2
✨ Added
- —
create-oke splits clean starters from teaching apps: templates/* is what a fresh scaffold copies, and examples/* stays behind --from-example. - —Export-size gate — the published surface is measured against
budgets.json on every run, so a regression fails the build instead of shipping.
♻️ Changed
- —Elements bind lazily, at first use, rather than at import time. Only what a Flow actually touches through
fx is constructed.
♻️ Changed
- —Publish pipeline prepared for both npm and JSR from one release run.
🐛 Fixed
- —
bun test no longer walks create-oke templates, which are copied rather than executed in place.
✨ Added
- —Dry-run publish shortcuts, so the release path can be rehearsed without touching a registry.
♻️ Changed
- —npm and JSR publishing folded into
ci.yml — one workflow, one gate set.
♻️ Changed
- —Cold-start budget raised to 75 ms, which is what a GitHub Actions runner can actually hold. A budget we cannot measure is not a budget.
🐛 Fixed
- —The cold-start gate runs on a quiet runner, isolated from the parallel suite, so its samples measure the kernel and not the neighbours.
- —Budget snapshots no longer auto-push;
budgets.json changes land as reviewable commits.
First published release. The one law is executable end to end.
✨ Added
- —
fx, the single door to the outside world, and the kernel that makes on(Trigger) → Effects run. - —All eight elements: Flow, Signal, Store, Clock, Gate, Vault, Channel, AI — with protocol-named drivers rather than vendor-named ones.
- —Manifest v1: schema, validation, and diff. The AoT compiler extracts it from source with oxc, and Standard Schema contracts are validated ahead of time.
- —Console on
:6533, with the Flows causality view, Traces and its folded timeline, Runs as wide events over Parquet and DuckDB, Signals, Store, and the remaining element panels. - —Agent MCP surface on
:6535. - —Typed client derived from the
App type with zero codegen. - —
.plug() with attachment-point scoping — app, unit, and flow. - —
oke CLI, infrastructure derived from the Manifest, and the four reference apps under examples/. - —
create-oke scaffold plus the release gates that guard every publish.