Releases are done via foundry to guarantee consistent sets of changes across developers. To perform a release:
-
Update the
CHANGELOG.mdwith a message (if not done so in the PR) -
Stage changes
git add -p
-
Run
./release.sh {{semver}}./release.sh {{semver}} # For example: # ./release.sh 1.2.0Under the hood,
./release.shwill:- Update the version in
package.json - Create a new
git commitfor "Release 1.2.0" - Create
git tagfor1.2.0 - Push
masterbranch - Push git tags
- Publish to
npm
- Update the version in