Releases are done via foundry
to guarantee consistent sets of changes across developers. To perform a release:
-
Update the
CHANGELOG.md
with 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.0
Under the hood,
./release.sh
will:- Update the version in
package.json
- Create a new
git commit
for "Release 1.2.0" - Create
git tag
for1.2.0
- Push
master
branch - Push git tags
- Publish to
npm
- Update the version in