-
Notifications
You must be signed in to change notification settings - Fork 3
Publish extension to market place
- Run
npm run lint
and clear all issues - Prepare release notes
- Update readme?
- Re-read all relevant comments in the code & update if necessary
Finalise release changes in the main branch. Create all release commits. Push changes to remote.
Type git tag
to see previous versions; you'll find something like:
v1.0.0
v1.0.1
v1.0.2
v1.0.3
v1.0.4
v1.0.5
v1.0.6
v1.0.7
v1.0.8
v1.0.9
v1.1.0
v1.1.1
v1.2.1
We use Semantic Versioning. This means the version format is in vX.Y.Z
.
Bump Z for bug fixes.
Bump Y for new features or serious updates.
Bump X for some major/fundamental change; or a bunch of changes together
tag your latest commit as follows:
git tag v3.0.0
Then push the new tag:
git push --tags
When you push a tag, the publish-extension.yml workflow triggers automatically.
Once the release completes, head over to Releases in github.
Click Draft a New Release
Choose the latest Tag.
Look at previous releases to fill in the title and description.
Tick "Set as latest release"
Click "Publish release"
Open the release list to verify that the latest tag is indeed the latest release. If not, tick "Set as latest release" again (IMPORTANT)
Finally, to test whether the release is successful in the market place an update should have been prompted in vs code extension:
https://marketplace.visualstudio.com/items?itemName=hexmos.Lama2