chore: publish npm releases to latest dist-tag - #8
Merged
Conversation
Drop --tag beta from release-please publish so merged releases update @latest automatically. Manual dist-tag promotion is no longer needed after the 0.2.0 bootstrap. Co-authored-by: Cursor <cursoragent@cursor.com>
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit a6b15f2. Configure here.
bird-m
self-requested a review
August 5, 2026 21:48
bird-m
approved these changes
Aug 5, 2026
ekim-amplitude
changed the title
ekim-amplitude
changed the title
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
2 participants
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.
Summary
Publish merged releases to npm
latestby default (remove--tag betafrom the release-please publish job).Change
pnpm publish ... --tag beta→pnpm publish ...(defaultlatest)Release gating is unchanged: release-please Release PR → merge →
npm-releaseenvironment → OIDC publish.Test plan
dist-tags.latestupdates without manualnpm dist-tagnpx @amplitude/developer-cli@latest --versionmatches new versionMade with Cursor