From 52d5e000e8b928627c97a4658c91722574262bdf Mon Sep 17 00:00:00 2001 From: heyitsaamir Date: Wed, 8 Jul 2026 09:25:15 -0700 Subject: [PATCH 1/4] docs: add GitHub Release step to CLI stable release process Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- RELEASE.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index ac6465d7e..4ef56f56a 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -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 patch:** + + Cut one GitHub Release per CLI patch version so the changes for each patch are discoverable. Tag it with the `cli-` prefix (matching the repo's `py-`/`js-`/`dotnet-` convention), targeting the merged release commit on `release/v3`. Scope the notes to `@microsoft/teams.cli` changes since the previous patch, and mark the newest release as `latest`. + + ```bash + gh release create cli-3.0.3 \ + --target "$(git rev-parse origin/release/v3)" \ + --title "Teams Developer CLI 3.0.3" \ + --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 .. --oneline -- packages/cli`) and summarize the notable fixes/features with their PR numbers. + +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. From 65d172a31679dcb087092a87cfb03caa2069df3f Mon Sep 17 00:00:00 2001 From: Aamir Jawaid <48929123+heyitsaamir@users.noreply.github.com> Date: Thu, 9 Jul 2026 11:30:05 -0700 Subject: [PATCH 2/4] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 4ef56f56a..2c9853450 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -81,9 +81,9 @@ Do not use a stable-looking version such as `3.1.{height}` for preview releases. Cut one GitHub Release per CLI patch version so the changes for each patch are discoverable. Tag it with the `cli-` prefix (matching the repo's `py-`/`js-`/`dotnet-` convention), targeting the merged release commit on `release/v3`. Scope the notes to `@microsoft/teams.cli` changes since the previous patch, and mark the newest release as `latest`. ```bash - gh release create cli-3.0.3 \ + gh release create "cli-" \ --target "$(git rev-parse origin/release/v3)" \ - --title "Teams Developer CLI 3.0.3" \ + --title "Teams Developer CLI " \ --notes-file notes.md \ --latest ``` From 2e7c4f98629a7c30bc2dff375c5437cd730902df Mon Sep 17 00:00:00 2001 From: Aamir Jawaid <48929123+heyitsaamir@users.noreply.github.com> Date: Thu, 9 Jul 2026 11:30:11 -0700 Subject: [PATCH 3/4] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 2c9853450..0c1e6303f 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -76,9 +76,9 @@ Do not use a stable-looking version such as `3.1.{height}` for preview releases. npm view @microsoft/teams.cli@latest version ``` -5. **Create a GitHub Release for the CLI patch:** +5. **Create a GitHub Release for the CLI stable version:** - Cut one GitHub Release per CLI patch version so the changes for each patch are discoverable. Tag it with the `cli-` prefix (matching the repo's `py-`/`js-`/`dotnet-` convention), targeting the merged release commit on `release/v3`. Scope the notes to `@microsoft/teams.cli` changes since the previous patch, and mark the newest release as `latest`. + Cut one GitHub Release per stable CLI version so the changes for each patch are discoverable. Tag it with the `cli-` 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-" \ From 053063a26366725c69f971473d9e4349bb88deb4 Mon Sep 17 00:00:00 2001 From: Aamir Jawaid <48929123+heyitsaamir@users.noreply.github.com> Date: Thu, 9 Jul 2026 11:30:20 -0700 Subject: [PATCH 4/4] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 0c1e6303f..62536393c 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -88,7 +88,7 @@ Do not use a stable-looking version such as `3.1.{height}` for preview releases. --latest ``` - To find the CLI changes since the previous patch, diff `packages/cli` between the two release commits (for example `git log .. --oneline -- packages/cli`) and summarize the notable fixes/features with their PR numbers. + To find the CLI changes since the previous patch, diff `packages/cli` between the two release commits (for example `git log .. --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`.