-
Notifications
You must be signed in to change notification settings - Fork 9
Releasing
Paul Jolly edited this page Jan 1, 2025
·
1 revision
Some WIP notes on the checklist to perform when cutting a new release with version $version
(e.g. v0.0.8
) of vscode-cue
:
- Ensure
extension.npm.version
in https://github.com/cue-lang/vscode-cue/blob/master/extension/extension.cue is updated to correspond to$version
, the version you plan to release, in a commit$commit
and that the trybots pass against this commit. -
Create a new tag
with
$version
against$commit
aschiefcueckoo
. - Verify that the trybot workflows run successfully
against
$version
. - Confirm that the new version of the extension is published to the VSCode marketplace; this is most easily
done by ensuring that
cueckoo@cue.works
receives a confirmation email, with a subject like:
[Succeeded] Extension publish on Visual Studio Marketplace - vscode-cue
- Verify that VSCode can successfully install the new version.
- Run the tests against this new version to ensure that all is well.