From 7e2dd5383af8a244501c5a86d737c75d66d67d92 Mon Sep 17 00:00:00 2001 From: Robin Malfait Date: Wed, 1 Oct 2025 18:25:46 +0200 Subject: [PATCH] Never publish v3 as `latest` on npm (#19043) This PR ensures that if we release v3 in the future, that we don't use `latest` as the npm tag, but `v3-lts` instead. Unfortunately we can't just use `3` or `v3` because they are not valid and you will get an error when trying to publish. Angular uses `v{n}-lts` for the versions they still support: https://www.npmjs.com/package/@angular/core?activeTab=versions Adding a tag is important, because omitting the `--tag` is the same as `--tag latest` --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 4554a07ae..9d3dfff06 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -45,7 +45,7 @@ jobs: echo "TAILWINDCSS_VERSION=$(node -e 'console.log(require(`./package.json`).version);')" >> $GITHUB_ENV - name: Publish - run: npm publish --provenance + run: npm publish --provenance --tag v3-lts env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}