ci: Release and Changelog automation#16
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Note
One thing that is missing after merging this PR (if we decide we want to merge ofc) - Setting the
RELEASE_TOKEN_GITHUBsecret in the project.Description
Clone of ionic-team/cordova-outsystems-geolocation#19
Automation for releases and changelog generation using semantic-release (which we already use in the Capacitor equivalent plugin).
The GitHub action does not trigger automatically on merge to main, you need to trigger yourself (since the release is exclusively on GitHub we can decide to change this to trigger on merge to main, since there's not much advantage of bundling changes in releases)
We should use angular commit convention
fix:commit message is a patch release (1.0.0->1.0.1)feat:commit mesasge is a minor release (1.0.0->1.1.0)BREAKING CHANGE:in commit footer triggers a major release (1.0.0->2.0.0)Context
Automate all Cordova Plugin releases - https://outsystemsrd.atlassian.net/browse/RMET-4428
Tests
Did some test releases in the fork (from which this PR is opened from), seems to be working fine.