Uupdated semantic commit message pattern matching and logic
- Updated pattern matching for
^fix:and^feat:to that it also now matchesfix(scope):style. - Added to echo statements to clearly echo previous version and new version
- Added logic to skip publishing if there's no change in version, if not a SNAPHOT
Testing steps
-
if snapshot version and a ^chore.*commit message, script should outputNo new package snapshot to publish as commit is type=chore -
if snapshot version and commit message is not chorethen script should outputNew package snapshot to publish: ${VERSION} -
if not a snapshot version and commit message is anything other than ^BREAKING CHANGE.*,^fix.*, or^feat.*, the.versionscript should outputNo new package version to publish-
otherwise the script should display the new version: New version to publish: ${VERSION}
-
-
test that commit messages fix:andfeat:publish a new version (if not a snapshot version) -
test that updated patterns to match a component name like fix(component):andfeat(component):also now publish a new version (if not a snapshot version) -
test that if a new version is to be published (PUBLISH_NEW_VERSION=true), the new rule for .publish:mavenruns the job-
otherwise if PUBLISH_NEW_VERSION=false, .publish:mavenjob is skipped
-
-
confirm that package with expected version is correctly published to Pacakge Registry
For #153 (closed)
Edited by Kevin Hooke