Repository navigation
v0.4.6
openapi-flow 0.4.6
Changes
GatherApiResponses now declares each results array position with JSON Schema
prefixItems, using the already-selected sourceNodeIds order. Each position
retains its original call identity, provenance and complete OAS body schema.
Downstream native settings can resolve a source-specific pointer from the actual
contract instead of guessing an array position or asking the user about an
implementation detail.
The existing runtime already emits that order before official Aggregate. API
completion and execution order, response data and types are unchanged. No
service-specific path, policy, field rewrite or automatic recovery was added.
Packages
Compatibility
Public function signatures and parameter shapes are unchanged. The gather output
schema is more precise: consumers inspecting its internal schema keywords should
read prefixItems rather than items.anyOf and membership constraints. A response
list reordered after gathering no longer satisfies this declared source order.
Rebuild derived native contracts and receipts from their actual materials rather
than reusing a stale snapshot. All three packages are version-aligned;
third-party dependency versions are unchanged.
Verification and limitations
Fourteen focused checks, fifty-nine original-OAS checks and five isolated n8n
2.37.10 gather conditions passed. The enabled suite passed 1,815/1,816 with only
the previously accepted Ajv special-key failure and no skips or cancellations.
Strict type/build, Lint, format and actual graph checks passed.
An independent consumer installed all three version-aligned candidate archives
without workspace links and passed strict TypeScript with library checks enabled
and runtime SDK compilation. This is candidate verification, not publication.
An actual-model replay with the corrected contract produced native settings that
met three isolated execution conditions, each preserving ten reads and their
original grouped bodies. Its source selection and downstream graph were fixed
verification materials; this is not a fresh whole-workflow, UI or single-pass
versus incremental quality result. A separate model proposal passed technical
checks but misstated a business rule. Contract validation alone does not prove
business intent, and this release makes no such guarantee.
The existing Ajv __proto__ limitation and upstream dependency audit warnings
remain disclosed. Package publication, host installation and service deployment
are separate steps. No business service was called for these engine checks.