Skip to content

Commit 3a5ece3

Browse files
committed
docs(release): API generation should be done after version bump
1 parent 01926e7 commit 3a5ece3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

release.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ Say the previous release was 0.0.J, the current release is 0.0.K, and the next r
1717

1818
- Make sure .gitignore and .npmignore are updated with any new files that need to be ignored.
1919

20-
- Generate new API documentation. Run `scripts/generate-docs.js`
21-
2220
- Update package.json with a version bump. If the changes are only bug fixes, increment the patch (e.g. 0.0.5 -> 0.0.6), otherwise increment the minor version.
2321

2422
- Update CHANGELOG.md.
@@ -31,6 +29,8 @@ Say the previous release was 0.0.J, the current release is 0.0.K, and the next r
3129
3230
- Breaking changes should be in their own section and include before/after examples of how to fix code that needs to change.
3331
32+
- Generate new API documentation. Run `scripts/generate-docs.js`
33+
3434
- Make a commit with the API and package.json changes titled chore(release): version bump and changelog for 0.0.K.
3535
3636
- Tag the release with `git tag 0.0.K`

0 commit comments

Comments
 (0)