chore: add release pipeline for the spec #539
Conversation
| --- | ||
| branches: | ||
| - master | ||
| - name: 2021-06-release |
There was a problem hiding this comment.
yes, we need to be hardcoded here 🤷🏼 believe me or not, this is also strange for me but semantic-release package doesn't support regex here (I tried everything). I will make sure this step is part of the release process procedure
|
Kudos, SonarCloud Quality Gate passed!
|
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
It is actually not included in the release. This was an unintentional release caused by the release automation initial run. 1.0 version of the spec was released a long time ago. The release mentioned by the bot was removed. |
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
Not included in release 2.1 yet, 2.1 was mistakenly triggered by our automation. |
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This PR introduces release automation for the spec using conventional commits spec and following the release cadence agreement.
assumptions:
fixPR and trigger patch releaseSee also: #536
Commit like
fix: spelling mistake in Operations object descriptionto master branchResults in a patch release (base was 2.0.1):
Commit like
feat: add something new in some non-release branchadded to branch that doesn't't follow pattern with-releasesuffxdid not trigger a release
Commit like
feat: add something new in release branchis a branch that has2021-06-releasesuffixResults in proper pre release
v2.1.0-2021-06-release.1Another commit to release branch
feat: add something more in release branchdoesn't close bump from 2.1 to 2.2 but proper bump of suffix from 1 to 2