Repository navigation
v0.10.1
0.10.1
Repeated schema projection now reuses validated preparation for the exact JSON declaration, including declarations cloned during material rebinding or checkpoint restoration. Preparation retains at most 32 resource contexts per process. Changing any source content requires a different preparation, even when its $id stays the same. Invalid JSON values and unresolved references remain errors; failed preparation is never retained.
Prepared resources are immutable internally. Public projected schemas remain independent mutable JSON values, so changing a returned schema cannot change another consumer's source contract. Reference enumeration for native output composition validates the selected source and pointer without constructing output schemas. Output schema generation and compilation retain their original contract checks.
Compatibility
Public function signatures, model tool schemas, source receipts and generated workflow behavior are unchanged. This is not a retry policy, a model/review budget increase, a reference-removal workaround or a host runtime upgrade. A bounded preparation cache can evict an entry; a later use then validates and compiles it again. Package consumers continue to own their Node runtime and deployment.
Verification and limitations
Source type checks, lint, formatting, focused recursive-resource and native-output tests, graph-document checks and local n8n 2.37.10 integration runs were exercised. Details and final counts are recorded in the verification record.
A private connection-step replay produced byte-identical model messages and output schema before and after this change. Its measured preparation time fell from approximately 25 seconds to approximately 3 seconds; separate instrumentation reduced compiling Ajv instances from 3,677 to 3 and compile calls from 7,354 to 6. These are measurements of one captured input, not a general latency guarantee or proof that an external connection failure is fixed. Private source documents, messages, responses and credentials are excluded from this repository.
The existing Ajv prototype-key runtime regression remains unresolved. Local execution tests include expected failures for invalid data and missing values; passing means those cases stopped at the expected boundary, not that invalid data was accepted. Full hosted-product generation, remote workflow registration and service deployment are separate checks.
Packages
Source synchronization, the matching annotated tag, public npm archive verification and the published GitHub Release are separate release steps. Product installation and deployment are reported separately.