search

Cratis / release-action

MIT License
0 stars 0 forks source link

Add support for SemVer based pre release branches #1

Open einari opened 3 months ago

einari commented 3 months ago

If the branch name is a semantic version number with a -{pre-release} string appended at the end, we should treat this as a pre-release and use the branch name as the basis for the version number. We would then append an incremental build number at the end .{build number}. This would result in a concatenated string looking like : {major}.{minor}.{patch}-{pre-release}.{build-number}, example : 10.0.0-beta.1.

Expose an output property that could be used to know if it is a pre-release build.

The goal is for projects to have version branches that continuously gets built on every commit to the branch. The flow would then open for feature branches off of the version branch. Whenever a PR finds its way into the version branch, it would then trigger such a release build.

For the output property exposed saying if it is a pre-release build, it could be then used to something like decide to deploy pre-releases to a different package repository or similar, entirely up to the repo.

woksin commented 3 months ago

I already have this functionality in my github action :) https://github.com/woksin-org/establish-context-action