@@ -3,19 +3,21 @@ Steps for releasing:
331 . Review open issues and PRs to see if any can easily be fixed, closed, or
44 merged.
552 . Bump copyright year in ` README.md ` , if necessary.
6- 3 . Review ` CHANGELOG.md ` for completeness and correctness. Update its
7- 4 . Bump the version in ` package.json ` .
8- 5 . Create a release PR containing the updates relating to any of the steps
6+ 3 . Consider whether any dependencies need to be updated.
7+ 4 . Review ` CHANGELOG.md ` for completeness and correctness. Update its
8+ release date.
9+ 5 . Set the version in ` package.json ` .
10+ 6 . Run ` npm publish ` . You can do this from the release branch. This will
11+ generate the docs, deploy docs, and publish the module to NPM.
12+ 7 . Create a release PR containing the updates relating to any of the steps
913 above.
10- 6 . Ensure that the release PR is merged into main.
11- 7 . With ` main ` checked out, run ` npm publish ` . This will generate the
12- docs, deploy docs, and publish the module to NPM.
13- 8 . Create and push a git tag (eg ` git tag v4.2.0 && git push --tags ` ).
14- 8 . Manually create a release on GitHub to include the release-specific
14+ 8 . Create and push a git tag (e.g. `git tag -a v4.2.0 -m v4.2.0 && git push
15+ --tags`).
16+ 9 . Manually create a release on GitHub to include the release-specific
1517 notes found in ` CHANGELOG.md ` .
16- 9 . Verify the release on
17- [ GitHub] ( https://github.com/maxmind/minfraud-api-node/releases ) and
18- [ NPM] ( https://npmjs.com/package/@maxmind/minfraud-api-node ) .
18+ 10 . Verify the release on
19+ [ GitHub] ( https://github.com/maxmind/minfraud-api-node/releases ) and
20+ [ NPM] ( https://npmjs.com/package/@maxmind/minfraud-api-node ) .
1921
2022## Set up pre-commit hooks
2123
0 commit comments