Have a feature request or found a bug in Watchbot processing? Please open an Issue. You're also welcome to propose a fix by submitting a pull request. A member of the @mapbox/data-platform team will review your PR.
The following steps outlines steps a member from Platform team can execute to publish a new test version
- Commit your changes to your test branch
- Run
npm run create:prerelease
. This will create a new version of the Watchbot CLI only- If this step fails, follow the manual steps outlined below:
- Create prerelease tag using
npm version prerelease
- Push changes and tags to GitHub by running
git push && git push --tags
- Find the gitsha you just pushed by running
git rev-parse HEAD
. You'll need this later. - Go to the staging CodePipeline (requires AWS login to
artifacts-stg
) - Update the codepipeline GitHub
Source
with your test branch name - Click
Release Change
and update theSource revision override
with your gitsha. You should find it in the dropdown list if you updated the branch name correctly.
- Verify staging CodePipeline ran successfully
- Run
npm run build
. This will build the npm package that provides the CDK construct. - Publish the new version to npm using
mbx npm publish --tag YOUR_NEW_TEST_TAG
The following outlines instructions Mapbox team members should follow to publish a new version of watchbot once a Pull Request has been reviewed and approved.
- Ensure the PR checklist is complete
- Merge the PR
- In your local copy, pull
master
to bring down the merge commit(s). - Ensure the correct version is updated in package.json and an entry in the changelog is added
- Run
npm run build
- There should NOT be any versioned introduced by this step
- Tag the new commit:
git tag v<new version number>
- Push the new commit and tags to Github:
git push --tags origin master
- Verify the binaries have been published using the AWS CodePipeline console (requires AWS login to
artifacts-prod
) - Publish the new version to npm using
mbx npm publish --access public
.