Currently, building a release is a two-step process - Most stuff is built on Linux, and some Windows-specific stuff (such as the Windows installer) is built on Windows. In the future, we’ll automate more of this process
artifactsdirectory to the Github release
yarn install && yarn run build)
yarn run build-win-installer
yarn run build-chocolatey
artifactsdirectory to Github release
Once all artifacts are attached to release (
latest_versionin _config.yml on the website. This updates the download URLs (
/latest.tar.gzetc) to point to the new release.
./update.shin releases repo then push changes
6963F07Ffor RPM and
9D41F3C3for Debian). Currently Daniel holds the private keys for these, ask him for the private keys if you need them.
git checkout 0.x-stable, e.g 0.7-stable
npm version patch, it will create a commit with changed package.json and tag
v0.xx.1to that commit
git push origin 0.x-stable --follow-tags