chore: rename package to @amplitude/developer-cli - #2
Merged
Conversation
Align npm metadata and synced source with the amplitude/developer-cli repo rename. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Align npm metadata and synced source with the amplitude/developer-cli repo rename.
This repo does not accept pull requests
@amplitude/developer-apiis published from an upstream source, so changescan't be merged here.
See CONTRIBUTING.md. Thanks!
Note
Medium Risk
Publishing and install paths change with the npm package name; releases depend on Trusted Publisher config for
@amplitude/developer-clibeing correct.Overview
Renames the published npm package and GitHub repo references from
@amplitude/developer-api/amplitude/developer-apito@amplitude/developer-cli/amplitude/developer-cliacross metadata and user-facing docs.package.jsonupdates the package name, homepage, repository URL, bugs URL, and keywords. README install/npxexamples use the new scope. CONTRIBUTING, the PR template, BUGBOT, and AGENTS titles point issue links and naming at the new repo. release-please workflow comments document npm Trusted Publishing for the new package and repo slug.A comment in
src/config.tsclarifies “Developer API” vs the old “developer-api” wording; API base URLs and runtime behavior are unchanged.Reviewed by Cursor Bugbot for commit adab435. Bugbot is set up for automated code reviews on this repo. Configure here.