[Bug]: npm 'latest' tag points to alpha release (0.1.7-alpha.2)

[murillodutt]

Description

The latest dist-tag on npm for sqlite-vec points to 0.1.7-alpha.2 (an alpha pre-release), not to the latest stable version 0.1.6.

This means npm install sqlite-vec installs an alpha version by default, which is unexpected behavior for users who expect latest to be a stable release.

Current npm State

latest  → 0.1.7-alpha.2   (alpha pre-release!)
alpha   → 0.1.7-alpha.10

Expected npm State

latest  → 0.1.6           (last stable release)
alpha   → 0.1.7-alpha.10

Impact

• Users running npm install sqlite-vec unknowingly get an alpha version
• The alpha has known bugs (shadow table NULLs, INSERT OR REPLACE failure)
• No way for users to install "latest stable" without knowing the exact version number
• Package managers with ^ version ranges may resolve to unexpected alpha versions

Suggested Fix

npm dist-tag add sqlite-vec@0.1.6 latest

This also affects all platform-specific packages:

• sqlite-vec-darwin-arm64
• sqlite-vec-darwin-x64
• sqlite-vec-linux-arm64
• sqlite-vec-linux-x64

Workaround

Users must explicitly pin the stable version:

"sqlite-vec": "0.1.6"

Reported by Murillo Dutt