vscode-marquee VS release-action

This and the desire for better DX is what motivated us (at Stateful) to introduce relevant onboarding information readily into Marquee - the high-density information homescreen for VS Code. As of Marquee v3.2.0 the beta UX of 🚀 Project Mode is available to you.

The term continuous integration and continuous delivery (short CI/CD) is a common best practice for software developers, including the ones building VS Code extensions. With the VS Code update from last November users have now access to pre-releases that allow developers to ship regular updates and offer testing out the latest cutting edge features from their extension to receive early feedback. In this blog post we’d like to share how Stateful releases its Marquee extension to the VS Code Marketplace and OpenVSX Registry through GitHub Actions. You can find a full example in the Marquee repository, feel free to copy and adapt it for your own extension.

Come find us either on GitHub, our community channels on Discord & Gitter, or through the in-Marquee feedback channels. Also take a look at the roadmap to see what's on Marquee's horizon.

sounds great! let us know if you have any feature requests: https://github.com/stateful/vscode-marquee/issues

I was able to get this mostly working with a combination of /u/ExTex5's script here, as well as the release action here

After all of that is done we create a release using the release-action action, located here and upload the app bundle we just generated as it will be needed in the next workflow step.

To conclude our release workflow we push our release commit and the new git tag back to GitHub, as well as attach the compiled extension file to the workflow using the ncipollo/release-action GitHub Action. This is intentionally done at the end of the workflow so that in case something went wrong during the process we don’t mark it as a new release: