@voltro/plugin-ai-flows 0.1.5 → 0.2.0

package/CHANGELOG.md

@@ -39,6 +39,22 @@ _Changes staged for the next release accumulate here (rolled up from
 
 ---
 
+## [0.2.0] — 2026-07-17
+
+### ⚠ BREAKING
+
+- **@voltro/cli** — The SQL dialect drivers (`@voltro/sql-postgres`, `@voltro/sql-mysql`, `@voltro/sql-mssql`, `@voltro/sql-sqlite`, `@voltro/sql-turso`) are no longer dependencies of `@voltro/cli`. Each app now declares the driver for its own DB dialect as a dependency, and `voltro dev`/`serve`/`migrate` resolve it from the app root. This keeps every driver — including turso's ~90 MB native binary — out of the production image of an app that doesn't use it: a `store: 'memory'` app ships no SQL driver at all, and a postgres app ships only `@voltro/sql-postgres`. Combined with a `pnpm --prod deploy`-based Dockerfile (the standalone/template Dockerfiles now do this), a memory-API image drops its `node_modules` from ~477 MB to ~330 MB. **Migration:** add the driver for your dialect to the app that uses it — `pnpm add @voltro/sql-postgres` (or `-mysql` for mysql/mariadb, `-mssql`, `-sqlite`, `-turso`). A memory store needs none. Scaffolded projects already declare it, and `voltro add mssql` adds `@voltro/sql-mssql` automatically. If the driver is missing at boot, `voltro serve` now fails with a message naming the exact package to install instead of an opaque module-not-found.
+
+---
+
+## [0.1.6] — 2026-07-17
+
+### Added
+
+- **@voltro/cli** — `voltro serve` now logs how long it took to become ready (`serve: ready in <n>ms`), and with `VOLTRO_BOOT_TIMING=1` breaks that total into per-phase timings — `modules` (node init + module-graph load/compile), `config`, `discover`, `store`, `plugins`, `workflow`, `ready`. This is the diagnostic for cold-start latency on scale-to-zero containers: read it from the container's own logs at its real CPU allotment to see which phase dominates. On a cold process the `modules` phase (evaluating the dependency graph) is almost always the largest, and no app-level change — precompiling the API with `voltro build` included — shrinks it; precompiling removes only the transpile of the app's own source files. The feature is a handful of `performance.now()` calls and one log line, safe to leave on in production.
+
+---
+
 ## [0.1.5] — 2026-07-16
 
 ### Added

package/THIRD-PARTY-NOTICES.md

@@ -5,7 +5,7 @@ property of its respective copyright holders and is used under the terms of
 its license. This file is provided for attribution; it grants no rights in
 @voltro/plugin-ai-flows itself, which is proprietary (see LICENSE).
 
-Generated from the resolved runtime dependency closure (61 packages).
+Generated from the resolved runtime dependency closure (60 packages).
 
 ---
 
@@ -3468,34 +3468,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 ```
 
-## @parcel/watcher-linux-x64-musl@2.5.6
-
-License: MIT
-
-```
-MIT License
-
-Copyright (c) 2017-present Devon Govett
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-```
-
 ## @standard-schema/spec@1.1.0
 
 License: MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voltro/plugin-ai-flows",
-  "version": "0.1.5",
+  "version": "0.2.0",
   "description": "AI Flows — durable multi-step AI pipelines (deterministic + agentic) with human-in-the-loop, chaining, and cadence. Author flows in code (defineFlow) or as data (visual editor rows); one engine runs both on @voltro/workflow durability, @voltro/ai generation, storage artifacts, and notifications.",
   "keywords": [
     "voltro",
@@ -57,15 +57,15 @@
     "node": ">=24.0.0"
   },
   "dependencies": {
-    "@voltro/ai": "0.1.5",
-    "@voltro/database": "0.1.5",
-    "@voltro/env": "0.1.5",
-    "@voltro/plugin-audit": "0.1.5",
-    "@voltro/plugin-multitenancy": "0.1.5",
-    "@voltro/plugin-soft-delete": "0.1.5",
-    "@voltro/protocol": "0.1.5",
-    "@voltro/runtime": "0.1.5",
-    "@voltro/workflow": "0.1.5"
+    "@voltro/ai": "0.2.0",
+    "@voltro/database": "0.2.0",
+    "@voltro/env": "0.2.0",
+    "@voltro/plugin-audit": "0.2.0",
+    "@voltro/plugin-multitenancy": "0.2.0",
+    "@voltro/plugin-soft-delete": "0.2.0",
+    "@voltro/protocol": "0.2.0",
+    "@voltro/runtime": "0.2.0",
+    "@voltro/workflow": "0.2.0"
   },
   "peerDependencies": {
     "effect": "^3.21.4"