In order to release a new version of the project:
- Update the package version with
npm version <version>
to apply that version across all sub packages. If the Major version has changed, the Macro name will be automatically updated by the sync-macro-version script - Push these changes (
git push --tags
) - Draft a new release in GitHub (the CI will do the publish to npm) with the same name as the version tag. If you select "pre-release", this will be published in NPM as a
next
label so it will only be installed by users who explictly request the@next
version.