Skip to content

docs: add CLI GitHub Release step to RELEASE.md #2913

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

Open
heyitsaamir wants to merge 4 commits into
base: main
Choose a base branch
from
Open

docs: add CLI GitHub Release step to RELEASE.md #2913

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
52d5e00
docs: add GitHub Release step to CLI stable release process
heyitsaamir Jul 8, 2026
65d172a
Potential fix for pull request finding
heyitsaamir Jul 9, 2026
2e7c4f9
Potential fix for pull request finding
heyitsaamir Jul 9, 2026
053063a
Potential fix for pull request finding
heyitsaamir Jul 9, 2026
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
16 changes: 15 additions & 1 deletion RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,21 @@ Do not use a stable-looking version such as `3.1.{height}` for preview releases.
npm view @microsoft/teams.cli@latest version
```

5. **Bump `main` for the next development cycle** if needed:
5. **Create a GitHub Release for the CLI stable version:**

Cut one GitHub Release per stable CLI version so the changes for each patch are discoverable. Tag it with the `cli-<version>` prefix, targeting the merged release commit on `release/v3`. Scope the notes to `@microsoft/teams.cli` changes since the previous stable tag, and mark the newest release as `latest`.

```bash
gh release create "cli-<version>" \
--target "$(git rev-parse origin/release/v3)" \
--title "Teams Developer CLI <version>" \
--notes-file notes.md \
--latest
```

To find the CLI changes since the previous patch, diff `packages/cli` between the two release commits (for example `git log <prev-tag>..<new-tag> --oneline -- packages/cli`), summarize the notable fixes/features with their PR numbers, and save that summary to `notes.md`.

6. **Bump `main` for the next development cycle** if needed:
- Edit `version.json` on `main`.
- For example, move to `"3.1-preview.{height}"` or `"3.1-beta.{height}"`.
- Commit and push via PR.
Expand Down