Automated release with version bump #5
Labels
ci
Continuous Integration
Comments
mohammedelgammal
added a commit
to mohammedelgammal/DataTome
that referenced
this issue
Jan 20, 2025
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
AlexandreHiroyuki
pushed a commit
that referenced
this issue
Jan 29, 2025
…27) * ci: Implementing Automated Version Release and Publish to PlatformIO 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 #5 * fix(ci): Library Release Versions Manipulation Improvement and Refactoring Pushing New Release Versions
|
@mohammedelgammal, the release Github action using semantic-release failed because the main branch cannot receive a commit directly, it has to be done through a pull request. Can you change it to open a PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Situation
When a new release is manually created on GitHub, an action is triggered to publish the package to PlatformIO registry.
Ideal Solution
If the field "version" is different between the files:
library.jsonlibrary.propertiesIt should trigger an error and not publish the package.
If the field "version" properly changed between commits on the main branch, tag the most recent commit with the version number.
The text was updated successfully, but these errors were encountered: