Release Process

Creating a vscode-meson release

The process is relatively simple:

1. Ensure that the CHANGELOG accurately reflects the changes that will be present in the new version
2. use bump2version to update the version, create the version bump commit, and create the tag, with either minor or patch as appropriate.
3. open the CHANGELOG with your editor and add a new ## next section at the top of the file
4. 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
5. download the created vsix from either registry
6. 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