From 1262c3003061c66863849bdd5131693f1ba1745e Mon Sep 17 00:00:00 2001 From: Alexander Pantiukhov Date: Tue, 17 Nov 2026 10:38:31 +0100 Subject: [PATCH] build(npm): Set publishConfig.tag=v8.28 on 8.28.x packages npm 11 refuses to implicitly move the `latest` dist-tag to a lower version. Publishing 8.28.1 while `latest` is 8.36.0 failed with "Cannot implicitly apply the latest tag" for both @sentry/react-native and @sentry/expo-upload-sourcemaps. Set `publishConfig.tag` to `v8.28` in both publishable packages. npm reads it at publish time when no --tag is passed, so 8.28.x backports go to the `v8.28` dist-tag and `latest` stays on the newest release. This is the same fix that release/8.14 uses (#6454). --- packages/core/package.json | 3 ++- packages/expo-upload-sourcemaps/package.json | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/packages/core/package.json b/packages/core/package.json index e9664f123d..7e879bebee 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -59,7 +59,8 @@ "ios" ], "publishConfig": { - "access": "public" + "access": "public", + "tag": "v8.28" }, "author": "Sentry", "license": "MIT", diff --git a/packages/expo-upload-sourcemaps/package.json b/packages/expo-upload-sourcemaps/package.json index db28ea2b6f..b9de60f00b 100644 --- a/packages/expo-upload-sourcemaps/package.json +++ b/packages/expo-upload-sourcemaps/package.json @@ -45,6 +45,7 @@ "node": ">=18" }, "publishConfig": { - "access": "public" + "access": "public", + "tag": "v8.28" } }