Repository navigation
v0.7.0
openapi-flow 0.7.0
Connection models now select the desired incoming relations and boundaries of
explicit target nodes with set-region. Core calculates additions and removals
against the accepted graph. Selecting an existing connection retains it instead
of adding a duplicate. Invalid duplicate selections, missing fields and protected
edge removal still fail explicitly; outputs are never silently repaired.
Confirmed independence is enforced before a partial graph is adopted. Necessary
connection candidates also use declared data dependencies and typed ordering,
route and join goals. These checks do not replace atomic whole-graph validation
or establish that arbitrary business semantics were understood correctly.
Root failures now identify actual incoming edges and failed preconditions. Step
feedback must match the exact current session, source and revision. The reference
host preserves the complete private rejection ledger and budget accounting while
sending only the latest current-revision rejection to the next step call. Its
ready-work scheduling policy prevents a blocked consumer bundle from repeatedly
starving necessary producer work; it creates no execution edges.
Compatibility
This minor release changes the step and connection-revision model wire contract.
Custom providers, mocks and recorded responses must replace model-generated
add/remove patches with node-local desired state. The old
WorkflowConnectionPatchSelection model type is replaced by
WorkflowConnectionRegionSelection. Core patch callers and returned decisions
retain their explicit patch API. Single ports are copied from the actual node
contract; multiple ports require explicit choices. Removed material nodes remain
explicit deletion choices. Historical feedback from another revision is rejected
before a model call. Existing checkpoints with accepted independence violations
are rejected instead of silently migrated. See the
contract and migration.
Step and revision structured-output schemas use standard local JSON references
to share endpoint choices. Custom model providers must support those references.
Packages
Verification and known limitations
Implementation checks passed 41 focused regressions, build/typecheck, lint,
formatting and six compiled-graph/document checks. Full tests passed 1,908 of
1,909; the previously documented Ajv handling of the literal __proto__
property remains a failing test and is not skipped or counted as passing.
Version-aligned checks passed 54 original-OAS regressions and independent
archive installation, strict typechecking and runtime compilation without
workspace symlinks or skipped library checks. Deterministic connection,
connection-revision and initial-material-recovery regressions passed ten isolated
n8n 2.37.10 executions and fifty local fixture requests, including baseline runs.
These synthetic runs establish engine behavior for their fixtures, not
natural-language planning accuracy or business-service behavior.
A private real-model connection-stage run used six prepared API calls and two
unchanged native configurations. It completed in 14 model calls after one goal
rejection and four connection rejections, producing six independent starts,
a six-input gather and a following comparison. Generated n8n JSON passed SDK
validation with no errors or warnings. Three earlier failed development runs
were retained and informed contract and scheduling changes. This is not a
controlled quality benchmark, a full browser generation, business API execution,
n8n engine verification or a service deployment. Latest-current feedback versus
no-feedback quality has not been compared experimentally.
Release archive and independent-consumer verification results are recorded in
the verification history. Private specifications, records, credentials,
model prompts and business responses are excluded from the public source and
packages. Dependency licenses, including n8n's conditions, apply independently.
External dependency versions are unchanged. Existing audit findings and engine
verification limits are recorded in the verification history; no clean audit or
full end-to-end success is claimed.
The current dependency audit reports 6 high and 11 moderate findings (17 total,
0 critical). These findings remain unresolved.