Skip to content

v0.3.16

Choose a tag to compare

@carefreelife98 carefreelife98 released this 25 Oct 13:14
· 53 commits to main since this release

openapi-flow 0.3.16

Keep all three packages aligned at 0.3.16. Node.js 24 or later and a compatible
host LangChain model are required.

Incremental connection planning

Core now owns serializable connection sessions, explicit goals, source/revision
receipts, atomic bundle validation, completion inspection, native-only material
extension and finalization through the existing complete DAG checks. Original OAS
contracts, API values and data bindings are not rewritten by a connection patch.

planWorkflowConnectionGoals interprets confirmed requirements once.
planWorkflowConnectionStep makes one structured call over the entire supplied
material/current graph and returns a decision plus a code-owned expectation.
Neither function hides a loop, applies its own output or requires per-node review.
See the usage guide.

The private LangGraph example composes an automatic, checkpointed child loop with
explicit call/rejection/deadline budgets and optional native material generation.
Its runtime clients and private exceptions stay outside checkpoint state. Native
planner stages now accept optional cancellation signals. Hosts own persistence,
business review, transport and UI; the example is not a fourth published package.
The previous single-pass connection APIs remain available.

Parallel all-input joins retain completed-producer proof from every compatible
branch. A real producer bypass and a mutually exclusive join still fail. API
argument failures also retain the underlying safe model/contract error diagnostic.

Verification and limits

Strict types, lint, formatting, 56 original-OAS checks, all 21 isolated n8n suite
commands, independent strict archive installation and package-content checks
passed. Unit results were 1,365/1,366, with only the retained Ajv special-key
failure; skipped and cancelled counts were zero.

A separate actual-model fixture automatically added one native join and accepted
three connection bundles in six model calls with zero rejected proposals. Four
isolated n8n executions and twenty loopback requests passed, including unchanged
upstream values and arrays. API selection/bindings were fixed test material; this
is not a full short-query workflow-quality or arbitrary-scale guarantee. Earlier
failed attempts and the completion-proof correction are retained in the release
record rather than counted as successes.

The Ajv properties.__proto__ limitation remains enabled. npm audit reports High 5
for the same previously accepted n8n SDK Zod 3 advisory/dependency set as 0.3.15;
the audit server's suggested-fix metadata changed, not the installed dependency or
advisory set. The automated gate therefore remains blocked, not a clean pass.
No external dependency version, exclusion or security override was changed.
The n8n dependency remains subject to its own Sustainable Use License.

See the release record
for source/publication provenance. npm publication, GitHub Release and service
deployment are separate states.