Summary
PR #15361 relaxed the @duckdb/node-api version pin from 1.4.2-r.1 to >=1.4.2-r.1 <1.6.0 to resolve downstream dependency conflicts. To ensure reliability across the full supported window, CI should validate both the minimum and a representative near-maximum version.
Requested by
@Akash504-ai — deferred from #15361 to keep that change minimal.
Tasks
Context
Summary
PR #15361 relaxed the
@duckdb/node-apiversion pin from1.4.2-r.1to>=1.4.2-r.1 <1.6.0to resolve downstream dependency conflicts. To ensure reliability across the full supported window, CI should validate both the minimum and a representative near-maximum version.Requested by
@Akash504-ai — deferred from #15361 to keep that change minimal.
Tasks
@duckdb/node-apito the minimum version (1.4.2-r.1)@duckdb/node-apito a representative 1.5.x version (e.g.,1.5.9)@mastra/duckdbtest suite under both pinned versionscloseSync/disconnectSync/close/disconnect, timestamp shape) passes at both bounds>=1.4.2-r.1 <1.6.0validatedContext
stores/duckdb/src/storage/db/index.tsalready contains defensive handling for multiple close method name variants, indicating known API variations across versions.