In this pr, I hope to introduce an automated release process for the project, aiming to reduce the workload of the release, and at the same time make it easier for other developers to freely choose and switch between the development version, alpha version, beta version, and official version.
Below I will introduce the specific usage details of the automatic release introduced by this PR.
If someone wants to make a new feature, he should make a new branch which name can't be dev, alpha or beta.
Commit with the correct title which should follow the rule down below.
After development, he should make a pull request to merge the branch into the dev branch (or merge directly).
After merging, the release workflow will auto-release a new dev version of this project.
We can do the same progress to release the main, alpha or beta version.
Commit message
Release type
fix(pencil): stop graphite breaking when too much pressure applied
Patch Fix Release
feat(pencil): add 'graphiteWidth' option
Minor Feature Release
perf(pencil): remove graphiteWidth option
BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reasons.
Major Breaking Release (Note that the BREAKING CHANGE: token must be in the footer of the commit)
First of all sorry for the late reply.
In this pr, I hope to introduce an automated release process for the project, aiming to reduce the workload of the release, and at the same time make it easier for other developers to freely choose and switch between the development version, alpha version, beta version, and official version.
Below I will introduce the specific usage details of the automatic release introduced by this PR.
dev
,alpha
orbeta
.dev
branch (or merge directly).main
,alpha
orbeta
version.fix(pencil): stop graphite breaking when too much pressure applied
PatchFix Releasefeat(pencil): add 'graphiteWidth' option
MinorFeature Releaseperf(pencil): remove graphiteWidth option
BREAKING CHANGE: The graphiteWidth option has been removed.
The default graphite width of 10mm is always used for performance reasons.
MajorBreaking Release(Note that the
BREAKING CHANGE:
token must be in the footer of the commit)Thanks for your review ❤.
Best regards, Asjdf