Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: set up continuous deployment from master with semantic-release (#…
…33) #### Description of changes *(note: this PR sets up semantic-release with `--dry-run`, so we can double check what it thinks it would do in the real build/release environment. There will be a second separate PR removing --dry-run)* Sets up [semantic-release](https://github.com/semantic-release/semantic-release) in its default configuration, which will run the following steps on every merge into master (after all the normal CI checks have passed only): * Look for the most recent "vX.Y.Z" tag in the repo * Look at all the merge commits to master since that point * If any contain `fix:` or `feat:` work, start a new release * Parse the commit messages as [Conventional Commits](https://www.conventionalcommits.org) to form release notes * Use `fix:`/`feat:`/`BREAKING CHANGE:` info in the merge commits to determine the next [semantic version](https://semver.org) * Bump the version in package.json/package-lock.json * Create a new GitHub release (via @ada-cat), which includes pushing a new git tag for the new version * run npm publish to publish the new version Note that the build step running semantic-release is conditionalized to only run on the master branch, and only in Pipelines that explicitly specify an opt-in variable. We will be using this to cause the publishing step to occur only from the secondary CI build I've set up with publishing credentials via @ada-cat and [accessibility-insights-team](https://www.npmjs.com/~accessibility-insights-team). #### Pull request checklist - [x] Addresses an existing issue: Implements user story #1492605 - [x] **n/a** Added relevant unit test for your changes. (`npm run test`) - [x] **n/a** Verified code coverage for the changes made.
- Loading branch information