actions
/
gh-action-bump-version
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
149 Commits 2 Branches 0 Tags 2.6 MiB
JavaScript 100%
Go to file
phips28 ba12820400 fix tag command 2019-10-26 21:47:47 +02:00
.github/workflows fixed depth 2019-10-26 21:11:45 +02:00
.gitignore added package lock 2019-10-26 21:09:42 +02:00
Dockerfile set git user 2019-10-26 21:42:48 +02:00
README.md README 2019-10-26 21:10:38 +02:00
action.yml new version with actions-toolkit 2019-10-26 21:06:00 +02:00
index.js fix tag command 2019-10-26 21:47:47 +02:00
package-lock.json added package lock 2019-10-26 21:09:42 +02:00
package.json new version with actions-toolkit 2019-10-26 21:06:00 +02:00

README.md

gh-action-bump-version

GitHub Action for automated npm version bump.

This Action bumps the version in package.json and push it back to the repo. It is meant to be used on every successful merge to master but you'll need to configured that workflow yourself. You can look to the .github/workflows/push.yml file in this project as an example.

Workflow

  • Check for the latest version number published to npm.
  • Based on the commit messages, increment the version from the lastest release.
    • If the string "BREAKING CHANGE" is found anywhere in any of the commit messages or descriptions the major version will be incremented.
    • If a commit message begins with the string "feat" then the minor version will be increased. This works for most common commit metadata for feature additions: "feat: new API" and "feature: new API".
    • All other changes will increment the patch version.
  • Push the bumped npm version in package.json back into the repo.
  • Push a tag for the new version back into the repo.