Commit 5e53f216dc33fd102d1acdef496b0972fb6d75df
2018-06-09T18:24:27
docs: update release steps to include clib manifest We've introduced a manifest for the clib version system that includes a version number; we should update it at release time to correspond with the version number in the header.
diff --git a/docs/release.md b/docs/release.md
index 42f032b..9c5b6a7 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -10,7 +10,8 @@ We aim to release once every six months. We start the process by opening an issu
Let's release v0.X, codenamed: <something witty>
- - [ ] Bump the versions in the headers
+ - [ ] Bump the versions in the headers (`include/git2/version.h`)
+ - [ ] Bump the versions in the clib manifest (`package.json`)
- [ ] Make a release candidate
- [ ] Plug any final leaks
- [ ] Fix any last-minute issues
@@ -27,6 +28,7 @@ Preparing the first release candidate includes updating the version number of li
- CHANGELOG.md
- include/git2/version.h
+- package.json
As soon as the pull request is merged, the merge commit shall be tagged with a lightweight tag.