-
-
Notifications
You must be signed in to change notification settings - Fork 741
Release Process
Paul edited this page Jul 28, 2020
·
8 revisions
This is the guide for maintainers:
- Pull the latest changes from master
- Create a branch
release-x.x.x
and switch to itgit checkout -b release-x.x.x
- Update version in
package.json
- Go through the commits in this release and write a changelog:
- Changelog should be written for humans (not for robots).
- Use simple wording explaining what the change is, how to use a new feature (maybe with a code example) and mention the related issue.
- When using
#123
a link for issue #123 will be automatically added. - A contributor must be mentioned. We use GitHub names with
@
prefix. A link to user profile is automatically added.
- Run
./runio.js docs
to build documentation - Commit all changes, push and create a PR
- Check that all tests pass and merge your PR
- Run
./runio.js release
to publish latest release. The website will be updated.
- To update version for patch release:
./runio.js release patch
- To update version for minor release:
./runio.js release minor
- Post announcements in Twitter & Slack
- Run
./runio.js docs:helpers
to build docs from helpers - Run
./runio.js publish:site
to update a website