Skip to content

Commit 635bdc5

Browse files
authored
Update the release plan for GHA
1 parent fd13745 commit 635bdc5

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

.github/release_plan.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -65,16 +65,14 @@
6565

6666
## Release
6767

68-
- [ ] Publish the release via Azure DevOps
69-
- [ ] Make sure [CI](https://github.com/Microsoft/vscode-python/blob/main/CONTRIBUTING.md) is passing. Try a re-run on any failing CI test stages. If tests still won't pass contact the owning team.
70-
- [ ] On Azure DevOps on the page for the CI run after it succeeds there will now be a "Releases" tab which is populated with a release entry. Click that entry to go to the release page, which shows the "Upload" and "Publish" stages
71-
- [ ] Click the deploy button on the "Upload" stage and make sure that it succeeds
72-
- [ ] Make sure no extraneous files are being included in the `.vsix` file (make sure to check for hidden files)
73-
- [ ] Click the deploy button on the "Publish" stage, this will push out the release to the public
74-
- [ ] From a VSCode instance uninstall the python extension. After the publish see if the new version is available from the extensions tab. Download it and quick sanity check to make sure the extension loads.
75-
- [ ] Create a [GitHub release](https://github.com/microsoft/vscode-python/releases)
76-
- [ ] The previous publish step should have created a release here, but it needs to be edited
77-
- [ ] Edit the tag to match the version of the released extension
68+
- [ ] Publish the release (🤖)
69+
- [ ] Make sure [CI](https://github.com/microsoft/vscode-python/actions?query=workflow%3A%22Insiders+Build%22) is passing
70+
- [ ] Download the artifact containing the VSIX and make sure no extraneous files are being included in the `.vsix` file (make sure to check for hidden files)
71+
- [ ] [Update the Marketplace](https://marketplace.visualstudio.com/manage/publishers/ms-python)
72+
- [ ] From a VS Code instance uninstall the python extension. After the publish see if the new version is available from the extensions tab. Download it and quick sanity check to make sure the extension loads.
73+
- [ ] Create a [GitHub release](https://github.com/microsoft/vscode-python/releases) (🤖)
74+
- [ ] Start creating a new release
75+
- [ ] Make the tag match the version of the released extension
7876
- [ ] Copy the changelog entry into the release as the description
7977
- [ ] Publish [documentation changes](https://github.com/Microsoft/vscode-docs/pulls?q=is%3Apr+is%3Aopen+label%3Apython)
8078
- [ ] Publish the [blog](http://aka.ms/pythonblog) post

0 commit comments

Comments
 (0)