Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: semantic release #227

Merged
merged 6 commits into from Oct 20, 2022
Merged

feat: semantic release #227

merged 6 commits into from Oct 20, 2022

Conversation

jasonschroeder-sfdc
Copy link
Collaborator

Adding Semantic Release to make automated releases.

Upon merging to a release branch [master, beta, alpha], semantic release will:

  • analyze commits to determine if a release is needed based on conventional-commit types
  • generate release notes
  • lerna publish it
  • make a GitHub Release (with release notes)
  • comment on all PRs that were included in this release, and all Issues in this release

As we don't want to release accidentally, this PR leaves on --dryRun --debug. We'll carefully watch the [master] build, if it goes well and calculates the expected release (v4.0.0), we'll turn those guardrails off in the next PR.

Add semantic-release configuration
Install the version-controlled dependencies from `package.json` and `yarn.lock`
- commit some assets as part of the version bump:
  - `CHANGELOG.md`
  - `**/package.json`
  - `yarn.lock`
- specify conventionalcommits style

Directly use `lerna publish` to push out a release
Tell Lerna to use conventional commits for changelog and versioning.
…commit messages

Allow conventional commit message format.
- update stale links
- modernize release steps
Add a badge to advertise the semantic-release feature.
@jasonschroeder-sfdc jasonschroeder-sfdc requested a review from a team as a code owner October 19, 2022 20:48
registry-url: 'https://registry.npmjs.org'

- run: yarn install --frozen-lockfile
- run: yarn run semantic-release --dryRun --debug
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be amended after the sanity test is passing.

Comment on lines +30 to +31
debug: true
dryRun: true
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This too (I'm extra cautious!)

@codecov
Copy link

codecov bot commented Oct 19, 2022

Codecov Report

Merging #227 (fa8e171) into master (f4813d4) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #227   +/-   ##
=======================================
  Coverage   97.83%   97.83%           
=======================================
  Files          22       22           
  Lines         323      323           
  Branches       66       66           
=======================================
  Hits          316      316           
  Misses          7        7           

@jasonschroeder-sfdc jasonschroeder-sfdc merged commit 6b7a180 into master Oct 20, 2022
@jasonschroeder-sfdc jasonschroeder-sfdc deleted the semantic-release branch October 20, 2022 05:43
github-actions bot pushed a commit that referenced this pull request Oct 20, 2022
## [4.0.0](v3.1.0...v4.0.0) (2022-10-20)

### ⚠ BREAKING CHANGES

* Explicitly supporting NodeJS 14.x and 16.x
* `sa11y` will no longer support Node.js 12, which is EOL since 30 April 2022

### Features

* remove support for Node.js 12 ([#116](#116)) ([43ade48](43ade48))
* semantic release ([#227](#227)) ([6b7a180](6b7a180))
* tsconfig package for tsconfig.json ([#174](#174)) ([5ff2fd2](5ff2fd2))
* webdriver7 ([#150](#150)) ([70dafc2](70dafc2))

### Bug Fixes

* set package.json node engines ([#228](#228)) ([42de911](42de911))
@github-actions
Copy link

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants