-
Notifications
You must be signed in to change notification settings - Fork 43
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
Compute release candidate #185
Comments
I think I gave the answer already in #183.
|
Problem with above is that it repeatedly creates the first release candidate, e.g. (1.2.0-rc.1):
I really don't see how calculating the next release candidate ( |
Ok, one really needs to go with the major version number only in the maintained-version (e.g. Got it working for my merge request pipelines: script:
- export CI_COMMIT_BRANCH=${CI_MERGE_REQUEST_SOURCE_BRANCH_NAME}
- LABEL=mr$CI_MERGE_REQUEST_IID
- semantic-release --allow-no-changes --allow-initial-development-versions --force-bump-patch-version --ci-condition-opt defaultBranch="*" -f .version --dry
- MAJOR=$(cat .version-unreleased|sed 's/\..*//')
- semantic-release --allow-no-changes --allow-initial-development-versions --force-bump-patch-version --ci-condition-opt defaultBranch="*" --maintained-version $MAJOR-$LABEL |
Hi,
I'd like to create release candidates on feature branches, i.e. compute the next version and append an -rc.1 etc.
The current beta-release-support requires a maintained version, but I would like to have that next version automatically computed from the found version and the commit analyzer.
Example:
Ideally, the label
rc
would also be variable, so that I can concurrently work on different feature branches.What would be a good approach to do this?
--maintained-version -rc
--maintained-version *-rc
--channel rc
Cheers, Manuel
The text was updated successfully, but these errors were encountered: