You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,13 +144,23 @@ Alternatively, you can run the tests inside of vscode. There are several vscode
144
144
145
145
## Releasing (write access required)
146
146
147
+
1. Double-check the `CHANGELOG.md` contains all desired change comments
148
+
and has the version to be released with date at the top.
149
+
1. Double-check that the extension `package.json` has the version you intend to release.
150
+
If you are doing a patch release (as opposed to minor or major version) this should already
151
+
be correct.
147
152
1. Trigger a release build on Actions by adding a new tag on master of the format `vxx.xx.xx`
148
153
1. Monitor the status of the release build in the `Release` workflow in the Actions tab.
149
-
1. Download the VSIX from the draft GitHub release that is created when the release build finishes.
154
+
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.
155
+
1. Optionally unzip the `.vsix` and inspect its `package.json` to make sure the version is what you expect,
156
+
or look at the source if there's any doubt the right code is being shipped.
150
157
1. Log into the [Visual Studio Marketplace](https://marketplace.visualstudio.com/manage/publishers/github).
151
158
1. Click the `...` menu in the CodeQL row and click **Update**.
152
159
1. Drag the `.vsix` file you downloaded from the GitHub release into the Marketplace and click **Upload**.
153
-
1. Publish the draft GitHub release and confirm the new release is marked as the latest release at <https://github.com/github/vscode-codeql/releases>.
160
+
1. Go to the draft GitHub release, click 'Edit', add some summary description, and publish it.
161
+
1. Confirm the new release is marked as the latest release at <https://github.com/github/vscode-codeql/releases>.
162
+
1. If documentation changes need to be published, notify documentation team that release has been made.
163
+
1. Review and merge the version bump PR that is automatically created by Actions.
0 commit comments