From cc00456cbc44c03f85634e42dde3ffa0c26b95de Mon Sep 17 00:00:00 2001 From: Robert Date: Wed, 21 Sep 2022 16:56:28 +0100 Subject: [PATCH] Clarify step of the release process --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d6f33c3d6ae..a489ec344d1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -160,6 +160,7 @@ From inside of VSCode, open the `launch.json` file and in the _Launch Integratio * **IMPORTANT** Make sure you are on the `main` branch and your local checkout is fully updated when you add the tag. * If you accidentally add the tag to the wrong ref, you can just force push it to the right one later. 1. Monitor the status of the release build in the `Release` workflow in the Actions tab. + * DO NOT approve the "publish" stages of the workflow yet. 1. Download the VSIX from the draft GitHub release at the top of [the releases page](https://github.com/github/vscode-codeql/releases) that is created when the release build finishes. 1. Unzip the `.vsix` and inspect its `package.json` to make sure the version is what you expect, or look at the source if there's any doubt the right code is being shipped.