You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing DuckDB as npm install @duckdb/duckdb-wasm, I currently get the latest tag which points to 1.28.1-dev106.0, which is an old prerelease. I expect instead to get the latest stable release which is currently 1.28.0. (If I want to install the latest prerelease, I can say npm install @duckdb/duckdb-wasm@next which correctly points to 1.28.1-dev159.0.)
To fix this, a maintainer needs to re-point the latest tag to 1.28.0 by running this command:
What happens?
When installing DuckDB as
npm install @duckdb/duckdb-wasm
, I currently get thelatest
tag which points to1.28.1-dev106.0
, which is an old prerelease. I expect instead to get the latest stable release which is currently1.28.0
. (If I want to install the latest prerelease, I can saynpm install @duckdb/duckdb-wasm@next
which correctly points to1.28.1-dev159.0
.)To fix this, a maintainer needs to re-point the
latest
tag to1.28.0
by running this command:Previously suggested #1591 (comment).
To Reproduce
Browser/Environment:
npm
Device:
macOS
DuckDB-Wasm Version:
N/A
DuckDB-Wasm Deployment:
N/A
Full Name:
Mike Bostock
Affiliation:
Observable
The text was updated successfully, but these errors were encountered: