-
Notifications
You must be signed in to change notification settings - Fork 50
Release Process
Dylan Baker edited this page Mar 31, 2023
·
1 revision
The process is relatively simple:
- Ensure that the CHANGELOG accurately reflects the changes that will be present in the new version
- use
bump2version
to update the version, create the version bump commit, and create the tag, with eitherminor
orpatch
as appropriate. - open the CHANGELOG with your editor and add a new
## next
section at the top of the file - push both the commits and the tag to upstream, this will start a github action which will deploy the updated vsix files to both OpenVSX and to the Microsoft registry
- download the created vsix from either registry
- Create a new github release, using the tag that was pushed, use the auto-populate feature to generate the release information, attach the visx file to the release