Skip to content

Latest commit

 

History

History
22 lines (19 loc) · 1.5 KB

RELEASE.md

File metadata and controls

22 lines (19 loc) · 1.5 KB
Raw

Releasing the extension

  1. Work in a branch. I sometimes go with ship-<version-num>, for example, ship-191.
  2. Find the current sprint using https://whatsprintis.it.
  3. Update the version to the major sprint number using npm version --no-git-tag-version THE_SPRINT_VERSION.
  • Replace THE_SPRINT_VERSION with patch if you are doing a bugfix release.
  1. Ensure the CHANGELOG is up to date.
  2. Update the service schema.
  3. Create a PR on GitHub, mostly for tracking reasons.
  4. Manually queue a Release build against your PR branch.
  • This will create a GitHub release at the commit you've specified!
  1. Ship the resulting package to the Marketplace.
  • You can grab it from either the pipeline run or off GitHub itself.
  1. Run npm version --no-git-tag-version patch so that packages produced by CI are treated as newer than the released version.
  2. Push that change and merge the PR. You can now delete the branch.

Bumping service schema

  1. Get the new schema from https://dev.azure.com/vscode-schema/_apis/distributedtask/yamlschema
  2. Replace service-schema.json with the results of that endpoint.
  3. In VS Code, run Format document to keep the diff readable.
  4. Update $comment with the Azure DevOps sprint info (you can see the sprint number in the lower left of the Azure DevOps UI at https://dev.azure.com/vscode-schema/).