Skip to content

chore: publish npm releases to latest dist-tag #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ekim-amplitude merged 1 commit into from
Aug 7, 2026
Merged

chore: publish npm releases to latest dist-tag #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/release-please.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ jobs:
# @amplitude/developer-cli to trust repo=amplitude/developer-cli,
# workflow=release-please.yml, environment=npm-release. No NPM_TOKEN.
#
# Pre-1.0 we publish to the `beta` dist-tag so `latest` stays unset until
# we promote at 1.0. Drop `--tag beta` when cutting 1.0.0.
# Default dist-tag is `latest` so `npm install @amplitude/developer-cli`
# and `npx @amplitude/developer-cli@latest` track each merged release.
- name: Publish the package to npm registry
run: pnpm publish --access public --no-git-checks --provenance --tag beta
run: pnpm publish --access public --no-git-checks --provenance
Loading