-
Notifications
You must be signed in to change notification settings - Fork 561
Release Checklist
Elliot Lee edited this page Jan 25, 2018
·
29 revisions
- Your changes should be on a branch.
- Your changes should have unit tests.
- Build your code with
yarn build - Run the unit tests with
yarn test - Get a full code review.
- Merge your branch into
developand push to github.
- Update
HISTORY.md- Update the version number and release date, and ensure it lists the changes since the previous release.
- Use
shasum -a 256 *to get the SHA-256 checksums. Add these to the file.
- Update
package.jsonto bump theripple-libversion number. - Merge
developintomasterand push to github.* - Create a release on github with an appropriate tag name (the version number).
- Publish the release to npm with
yarn publish
*This is important because we have docs telling developers to use master to get the latest release.