From 700d16f99344e2597ac43aaa131c353e0d4146e9 Mon Sep 17 00:00:00 2001 From: Chuan-kai Lin Date: Mon, 8 Dec 2025 11:45:55 -0800 Subject: [PATCH] Release plan: add step to verify extension publishing --- docs/releasing.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/releasing.md b/docs/releasing.md index cb46ab61dfb..a8696cacdf7 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -56,6 +56,7 @@ - If there is an authentication failure when publishing, be sure to check that the authentication keys haven't expired. See below. 1. Go to the draft GitHub release in [the releases page](https://github.com/github/vscode-codeql/releases), click 'Edit', add some summary description, and publish it. 1. Confirm the new release is marked as the latest release. +1. Confirm that the new release is available on the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-codeql) and on the [Open VSX Registry](https://open-vsx.org/extension/GitHub/vscode-codeql). 1. If documentation changes need to be published, notify documentation team that release has been made. 1. Review and merge the version bump PR that is automatically created by the Release workflow.