chore(main): release developer-cli 0.2.0 - #7
Merged
ekim-amplitude merged 2 commits intoAug 5, 2026
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Changelog leaks private repo name
- Rewrote the changelog feature entry to say upstream instead of naming the private repo and sync SHA.
Or push these changes by commenting:
@cursor push c4330bf8d1
Preview (c4330bf8d1)
diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,7 +6,7 @@
### Features
* import amp CLI distribution ([#1](https://github.com/amplitude/developer-cli/issues/1)) ([976f4f7](https://github.com/amplitude/developer-cli/commit/976f4f7f258865ac78f27a8bda3c36956d27fc97))
-* sync developer-cli from amplitude/javascript@1b44da248692 ([#4](https://github.com/amplitude/developer-cli/issues/4)) ([ce7ed11](https://github.com/amplitude/developer-cli/commit/ce7ed11346b5ebd452d29f1a64a88c575628425e))
+* sync developer-cli from upstream ([#4](https://github.com/amplitude/developer-cli/issues/4)) ([ce7ed11](https://github.com/amplitude/developer-cli/commit/ce7ed11346b5ebd452d29f1a64a88c575628425e))
### Bug FixesYou can send follow-ups to the cloud agent here.
Reviewed by Cursor Bugbot for commit 592e925. Configure here.
Collaborator
Public docs should not name the private upstream monorepo or sync SHA. Applied via @cursor push command
ekim-amplitude
approved these changes
Aug 5, 2026
ekim-amplitude
deleted the
release-please--branches--main--components--developer-cli
branch
August 5, 2026 16:34
Contributor
Author
|
🤖 Created releases: 🌻 |
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.


🤖 I have created a release beep boop
0.2.0 (2026-08-04)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Low Risk
Version and changelog-only release metadata with no application or CI logic changes in the diff.
Overview
Release Please bumps
@amplitude/developer-clifrom 0.1.0 to 0.2.0 and records the release in version metadata.The new CHANGELOG section for 0.2.0 documents prior work: importing the amp CLI distribution, syncing from upstream, and release fixes (OIDC npm publish and GitHub App secrets on the
npm-releaseenvironment). This PR does not change runtime CLI code—only version and changelog files.Reviewed by Cursor Bugbot for commit 8e70a7f. Bugbot is set up for automated code reviews on this repo. Configure here.