Determine Release Creation in GitHub from Azure DevOps Pipelines

[clarkio]

Right now I have to still manually publish the release in GitHub. The thought behind doing that is in case people would prefer to install from there and to keep a separate backup/history of the versions between packages.

It would be nice to automate this (I'm confident it's possible) process as part of the pipelines somehow.

[parithon]

Here are some docs on how to accomplish this goal:

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/github-release?view=azure-devops

[parithon]

We could do the following to update the <major>.<minor>.<patch> version of the package.json prior to publishing to the Marketplace, then pull that change out to create the Github release tag.

Updates the version from 0.1.4 (current version as of this comment) to 0.1.5:

vsce publish patch
version=$(node -p "require('./package.json').version")

[gavinbarron]

You can then add that captured variable to your pipeline using this `echo "##vso[task.setvariable variable=packageVersion]$version"

Documentation