Repository navigation
v0.5.0
openapi-flow 0.5.0
0.5.0 introduces goal-aware connection outlines, opt-in material revision
requests, native source subsets and explicit numeric-query pagination.
Changes
Connection outlines keep every accepted session goal. Core derives
associations from typed goals and actual nodes, retains semantic and
cross-bundle goals as global work, and distinguishes local and global bundles.
Trace IDs and completed local bundles do not prove whole-workflow goal
satisfaction.
planWorkflowConnectionStep adds optional allowMaterialRevisions, default
false. Explicit opt-in lets the model request replanning of eligible
existing materials. Core's createWorkflowConnectionMaterialRevisionRequest
and validateWorkflowConnectionMaterialRevisionRequest bind requests to the
current source, session, revision and permitted targets. Requesting a revision
does not apply it: the host still owns stage dispatch and validated adoption
through the existing revision API. The library source provides this request
boundary; automatic host dispatch and its integration are not yet verified.
Native source selection permits a subset of selected materials to be
referenced by actual settings, without inventing execution dependencies.
Unselected or invalid references still fail. Repeated native-selection
material contexts are pooled on the model wire without changing original
values, schemas or receipts.
The source also adds explicit numeric-query HTTP Request pagination. It uses
official n8n pagination settings, validates the bounded sequence against the
original OAS contract and preserves each page's original response envelope.
Request-budget and status-code termination are explicit. Natural-language
pagination planning and automatic host orchestration are not integrated.
Generic IF/conditional loops, body-parameter pagination,
response-body/empty-body termination and next-URL traversal are excluded.
Packages
Compatibility
The stored outline contract is breaking: goalIds, globalGoalIds and each
bundle's scope belong to the validated stored contract. Regenerate older
outlines from the original current source and accepted session. Missing fields
are rejected; no silent migration or inferred replacement is provided.
Material revision requests are opt-in. Omitted or false
allowMaterialRevisions preserves the prior model wire contract. All three
packages and their exact internal dependencies are aligned at 0.5.0;
third-party dependency versions are unchanged.
Verification and limitations
Verification recorded for the checked source reports 1,850/1,851 tests passing
with the one previously accepted Ajv __proto__ failure, all static checks
passing and 6/6 stage replays passing. Live outline planning used one logical
call: HTTP 429 was followed by HTTP 200 through the existing route. Logical
calls and HTTP attempts are different counts.
Replay and outline results do not establish final generated-workflow quality,
fresh business execution, UI acceptance or single-pass versus incremental
quality. The Ajv limitation remains accepted and unfixed. Automatic revision
dispatch remains source-only and unverified in the host. Package publication,
local host adoption and service deployment are separate outcomes.
The fresh audit of the checked dependency graph reports five High affected
entries, with Info, Low, Moderate and Critical all zero. These are the
previously accepted n8n SDK/config/expression dependency findings involving
Zod 3.25.76 and
GHSA-mrhx-c7xc-m3w5:
@n8n/config, @n8n/expression-runtime, @n8n/workflow-sdk, n8n-workflow
and Zod. Five affected package entries do not mean five distinct
vulnerabilities or proven application exploits. The audit reports
fixAvailable: false for the SDK; it is not a claim that no fix can ever
exist. This carries forward the security limitation disclosed in 0.4.6.
Third-party versions are unchanged; no Zod 3-to-4 override, SDK downgrade or
advisory exclusion is included. This release does not claim a clean audit.
Source and audit provenance, npm publication and downloaded archive integrity
are verified separately from these source checks.