This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
ci: use semantic commits to determine next release version and fix final merge step #2979
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidmurdoch
commented
Apr 25, 2022
cds-amal
approved these changes
Apr 26, 2022
davidmurdoch
changed the title
davidmurdoch
force-pushed
the
master-test
branch
2 times, most recently
from
b567fc3
to
7acc56a
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our previous release mostly worked (it failed to auto-merge back into the develop branch) but had the wrong version number for the next feature release. The release process wasn't detecting feature commits, which would cause feature releases to be versioned incorrectly (patch update instead of a minor update). This PR should fix both of these issues.