[FEQ] Added semantic releases automation #36
Conversation
adrienne-deriv
commented
Apr 4, 2024
adrienne-deriv
commented
- Integrated semantic release automation
- Ensure that NPM_TOKEN is set in secrets, as well as the current version is already tagged (semantic release will use the current tag as reference of the current version)
| "+([0-9])?(.{+([0-9]),x}).x", | ||
| "master", | ||
| "next", | ||
| "next-major", |
There was a problem hiding this comment.
Any commits to the branches next, next-major will append a prelease version, like 0.0.11-beta
release.config.cjs
Outdated
| releaseRules: [ | ||
| { | ||
| type: "feat", | ||
| release: "minor", |
There was a problem hiding this comment.
These are the release rules, which dictates what version it should be bumped to. The type of releases feat, build, chore are all checked within your commits.
So if you commited something like chore: updated time.ts and merged it to master branch, then the version will be patched from 0.0.11 to 0.0.12, likewise if you commited something like feat: added language utilites and merged it to master, the version would be bumped minor from 0.0.11 to 0.1.11
| env: | ||
| CI: true | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| NPM_TOKEN: ${{ secrets.NPM_TOKEN}} |
There was a problem hiding this comment.
Ensure that NPM_TOKEN is already set in the secrets.
Also, make sure that there is already a tag for the latest version. semantic-release will use the latest tag as a reference of the current version and either bump/patch the current version when merged to master
…iv/deriv-utils into semantic-release-automation
Pull Request Test Coverage Report for Build 8566861173Details
💛 - Coveralls |
| permissions: | ||
| contents: read # for checkout |
There was a problem hiding this comment.
@adrienne-deriv, can this be at the job level or is it needed globally?
There was a problem hiding this comment.
The job already has contents: write permission, so this is redundant, I'll remove it
|
🎉 This PR is included in version 0.0.12 🎉 The release is available on: Your semantic-release bot 📦🚀 |
