Repository navigation
build(npm): Set publishConfig.tag=v8.28 on 8.28.x packages - #7047
Merged
Merged
Conversation
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).
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog.
🤖 This preview updates automatically when you update the PR. |
Contributor
alwx
marked this pull request as ready for review
November 17, 2026 09:41
antonis
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📢 Type of change
📜 Description
Add
"tag": "v8.28"underpublishConfigin@sentry/react-nativeand@sentry/expo-upload-sourcemaps. When no--tagis given on the command line, npm uses this tag at publish time.💡 Motivation and Context
The 8.28.1 publish failed. npm 11 does not move the
latesttag to a lower version (latestis now 8.36.0):Cannot implicitly apply the "latest" tag ... You must specify a tag using --tag. This is the same fix as #6454 onrelease/8.14.Failed run: https://github.com/getsentry/publish/actions/runs/44056049883/job/133945600807
💚 How did you test it?
I ran
npm publish --dry-runon a copy ofexpo-upload-sourcemapswith version 8.28.1. Without the tag, I get the CI error. With the tag, the check passes.📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Close getsentry/publish#10459, delete
release/8.28.1, and run prepare for 8.28.1 again fromrelease/8.28.