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
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: