Closed carlopi closed 2 weeks ago
(relying on CI to actually check this)
Merging, checking CI on main, then tagging, solves https://github.com/duckdb/duckdb-node/issues/138
There is an issue also on v1.1.2 on npm (https://github.com/duckdb/duckdb-node/issues/135), that is also solved by this.
@hannes: do we want also v1.1.2 in? I think there are no proper uses, so I cut that corner.
I think 113 is enough thanks
(relying on CI to actually check this)
Merging, checking CI on main, then tagging, solves https://github.com/duckdb/duckdb-node/issues/138
There is an issue also on v1.1.2 on npm (https://github.com/duckdb/duckdb-node/issues/135), that is also solved by this.