Releasing a New Version

To release a new version of klighd-vscode, the package versions habe to be updated and a new release on GitHub published.

• Updating the package versions: Run the command npx lerna version --no-git-tag-version to interactively update the version of each package in the monorepo. Without any options lerna commits the change, creates tags, and pushes them to the remote. However, the commit creates a tag for each package. To avoid multiple tags, use --no-git-tag-version. Afterwards, commit the changes and push the new commit to the remote.
• Create a new release branch: it should be named vx.y.z-release. Continue from this branch.
• Make the build process production-ready: In the klighd-cli and klighd-vscode package.json files change the build script to production mode with no specific --devtool parameter to better pack the artifacts for production use. See this commit as a reference.
• Create a release tag: create a tag with git tag <version> on this updated release branch and push it to remote.
• Publish a GitHub release: In the last step, the new release has to be published as a GitHub release to trigger the publish workflow, which distributes the applications. For the release, select the previously published tag as an existing tag for the release. Add some release notes and click "Publish release". Pro-tip: the release notes can be maintained as a draft release during development. The workflow is only triggered when the draft release is published.