Conversational reporting mailer
Builds reporting emails and call the Chat's email API to send them
Publishing
Before publishing, remember to consider the effects your changes have for our users. See semantic versioning.
Script prepare
will run before publishing automatically.
Don`t publish something else by accident. If you did, unpublish it within 72 hours.
For publishing, you need access to giosg organization in npm. You can request that from one of the organization admins or request them to publish the package.
- Update CHANGELOG.md, update package version (e.g. with
npm --no-git-tag-version version <major|minor|patch>
), and commit. - Create pull request.
- Request a review from another experienced developer.
- Merge the pull request after approval and passed tests.
- Pull master locally.
- Login to npm with
npm login --scope=giosg
. You will be prompted for credentials. - Publish the package with:
npm publish --access public
. --access public
flag is mandatory because organization packages default to restricted
. - Create a new tag on the latest commit on master branch
git tag vX.Y.Z
X.Y.Z
being the published version. - Push the tag to remote
git push --tags
.