Files

Andrew Calcutt 43e52d054e Update node release based on maplibre-js release workflow - v2 with changelog (#1995 )

Co-authored-by: mwilsnd <mwilsnd@gmail.com>
Co-authored-by: Bart Louwers <bart@emeel.net>
Co-authored-by: Bart Louwers <bart.louwers@gmail.com>

2024-01-08 12:51:31 -05:00

Instructions for making a Node release

Change the version number in package.json. on the command line, in the package root directory, run the following command, replacing <update_type> with one of the semantic versioning release types (prerelease, prepatch, preminor, premajor, patch, minor, major):

npm version <update_type> --preid pre --no-git-tag-version

Update the changelog, which can be found in platform/node/CHANGELOG.md. The heading must match ## <VERSION> exactly, or it will not be picked up. For example, for version 5.2.0:

## 5.2.0

Commit and push the changes. On push the 'node-release' workflow will automaticlly check if the release has been published on npm. If the release has not yet been published, the workflow will build the node binaries and upload them to a new github release, then publish a new npm release.