From ba7694dd13ae1389e204dbf0fcf7b8d4d49880b1 Mon Sep 17 00:00:00 2001
From: Carlo Piovesan <piovesan.carlo@gmail.com>
Date: Mon, 29 Jan 2024 14:17:16 +0100
Subject: [PATCH] Publish dev version on npm to @next instead of @latest

Suggested here https://github.com/duckdb/duckdb-wasm/issues/1561#issuecomment-1888346358 by @mbostock

Fixes https://github.com/duckdb/duckdb-wasm/issues/1591
---
 .github/workflows/main.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 67dc7b6fa..8cfbf303e 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -1056,8 +1056,10 @@ jobs:
             - name: Publish to NPM
               env:
                   NODE_AUTH_TOKEN: ${{ secrets.NPM_PUBLISH_TOKEN }}
+                  TAG: ${{ startsWith(github.head_ref, 'v') && 'latest' || 'next' }}
               if: env.NODE_AUTH_TOKEN != null
               run: |
+                  echo "${TAG}"
                   ./scripts/npm_publish_lib.sh
                   ./scripts/npm_publish_shell.sh
                   ./scripts/npm_publish_react.sh