fix(publish): exclude sqlite-wasm from publish flow

Author: NathanFlurry

.github/workflows/publish.yaml

@@ -435,7 +435,7 @@ jobs:
 
       # ---- build TypeScript packages (turbo dep graph picks up native) ----
       - name: Build TypeScript packages
-        run: pnpm build -F rivetkit -F '@rivetkit/*' -F '!@rivetkit/shared-data' -F '!@rivetkit/engine-frontend' -F '!@rivetkit/mcp-hub' -F '!@rivetkit/sqlite-native' -F '!@rivetkit/rivetkit-native'
+        run: pnpm build -F rivetkit -F '@rivetkit/*' -F '!@rivetkit/shared-data' -F '!@rivetkit/engine-frontend' -F '!@rivetkit/mcp-hub' -F '!@rivetkit/sqlite-native' -F '!@rivetkit/sqlite-wasm' -F '!@rivetkit/rivetkit-native'
 
       - name: Pack inspector
         run: npx turbo build:pack-inspector -F rivetkit

scripts/publish/src/ci/bin.ts

@@ -337,7 +337,6 @@ program
 			`npm install rivetkit@${tag}`,
 			`npm install @rivetkit/react@${tag}`,
 			`npm install @rivetkit/rivetkit-native@${tag}`,
-			`npm install @rivetkit/sqlite-wasm@${tag}`,
 			`npm install @rivetkit/workflow-engine@${tag}`,
 			"```",
 			"",

scripts/publish/src/lib/packages.ts

@@ -8,12 +8,13 @@
  * those optionals at install time, so they must exist on the registry before
  * anyone installs the meta.
  *
- * NOTE: `@rivetkit/sqlite-native` is deliberately NOT discovered here. The
- * sqlite-native Rust crate is now statically linked into
- * `@rivetkit/rivetkit-native` via `libsqlite3-sys` + the `rivetkit-sqlite-native`
- * workspace dep, so the standalone npm package is redundant. The committed
- * `rivetkit-typescript/packages/sqlite-native/*` tree is deprecated and stays
- * on the registry at its last published version.
+ * NOTE: `@rivetkit/sqlite-native` and `@rivetkit/sqlite-wasm` are deliberately
+ * NOT discovered here. The sqlite-native Rust crate is now statically linked
+ * into `@rivetkit/rivetkit-native` via `libsqlite3-sys` +
+ * the `rivetkit-sqlite-native` workspace dep, so the standalone npm package is
+ * redundant. The old sqlite-wasm package was removed from the workspace but
+ * its package.json remains for compatibility. Both stay on the registry at
+ * their last published versions.
  */
 import { execSync } from "node:child_process";
 import { existsSync, readFileSync, readdirSync, statSync } from "node:fs";
@@ -41,6 +42,7 @@ export const EXCLUDED = new Set<string>([
 	"@rivetkit/engine-frontend",
 	"@rivetkit/mcp-hub",
 	"@rivetkit/sqlite-native",
+	"@rivetkit/sqlite-wasm",
 	"example-agent-os",
 	"example-agent-os-e2e",
 ]);

scripts/publish/src/local/cut-release.ts

@@ -154,7 +154,7 @@ async function main() {
 		await $({
 			stdio: "inherit",
 			cwd: repoRoot,
-		})`pnpm build -F rivetkit -F @rivetkit/* -F !@rivetkit/shared-data -F !@rivetkit/engine-frontend -F !@rivetkit/mcp-hub -F !@rivetkit/sqlite-native -F !@rivetkit/rivetkit-native`;
+		})`pnpm build -F rivetkit -F @rivetkit/* -F !@rivetkit/shared-data -F !@rivetkit/engine-frontend -F !@rivetkit/mcp-hub -F !@rivetkit/sqlite-native -F !@rivetkit/sqlite-wasm -F !@rivetkit/rivetkit-native`;
 		await $({
 			stdio: "inherit",
 			cwd: repoRoot,