Releasing

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 $version (the version you plan to release) is reflected in:

  • extension.npm.version in extension/extension.cue (without its v prefix).
  • version and packages[""].version in extension/package-lock.json (without its v prefix).

• Ensure that the trybots pass against the commit that updates/aligns $version in the above locations ($commit).

• Make sure that a correctly scoped Personal Access Token exists for the Microsoft account that has permissions to update the extension in the Marketplace.

  • It appears that expired PATs are entirely deleted from the Azure DevOps UI, as opposed to persisting alongside some marker that they've expired. Therefore an empty PAT UI page ("No Personal Access Tokens exist") doesn't necessarily indicate that you're logged in with the incorrect Microsoft account.

• Create a new tag with $version against $commit as chiefcueckoo.

• 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
  

  Alternatively, check the More Info >> Version field at the bottom right of the extension's Marketplace page.

• Verify that VSCode can successfully install the new version.

• Run the tests against this new version to ensure that all is well.