ci: Implementing Automated Version Release and Publish to PlatformIO #27
Conversation
docs: Assuring conventional commits - This PR changed: [prlint.yml]: Validates every PR against Conventional Commits to guarantee a healthy release and publish. [release.yml]: Automates releasing a new version including all the necessary steps using semantic-release action. Must pass prlint and tests CIs. [publish.yml]: Automates publishing the new released version to PlatformIO registry and update versions in library.json and library.properties files. Depends on [release.yml]. [CONTRIBUTING.md]: Added note for new contributors about conventional commit message. resolves issue AlexandreHiroyuki#5
There was a problem hiding this comment.
How can you guarantee the library version update script to run before publishing it to PlatformIO?
There was a problem hiding this comment.
To guarantee a library version update before publishing:
1- The [Publish to PlatformIO] only triggers when there is a new release on GitHub so the tag is guaranteed to be different.
2- Even in case there is a new release tag is out it double checks if [$LATEST_TAG] is different from the current library versions [$LIB_V] and [$PROPS_V] before update and publishing (updated in latest commit: exits with error if there are no changes or any of files manipulations fails)
|
Again, thank you for dedicating your time to solving a CI issue. I never thought someone would pay attention to a matter that's not the core code. |
…oring Pushing New Release Versions
docs: Assuring conventional commits
resolves issue #5