You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Decide on the new version number and update it within the `package.json` file. This will be used as the NPM version number.
5
+
* Write the CHANGELOG.md entry for the release by looking at the PRs.
6
+
* Commit `package.json` (for version number) and `CHANGELOG.md`.
7
+
* Push a tag for the version that exists in the `package.json` using `git tag {version}` and `git push origin {tag}`. Pushing this tag will cause Travis to build the Node bindings for all currently supported platforms to verify that they build correctly. If they do, it will then perform the NPM publish step within TravisCI via the `publish.js` script.
0 commit comments