1b71093a0a | ||
---|---|---|
.github/workflows | ||
.gitignore | ||
Dockerfile | ||
README.md | ||
action.yml | ||
index.js | ||
package-lock.json | ||
package.json |
README.md
gh-action-bump-version
GitHub Action for automated npm version bump.
This Action bumps the version in package.json and pushes 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.
Attention
Make sure you use the actions/checkout@v2
action!
Workflow
- Based on the commit messages, increment the version from the latest release.
- If the string "BREAKING CHANGE", "major" or the Attention pattern
refactor!: drop support for Node 6
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" or includes "minor" then the minor version will be increased. This works
for most common commit metadata for feature additions:
"feat: new API"
and"feature: new API"
. - If a commit message contains the word "pre-alpha" or "pre-beta" or "pre-rc" then the pre-release version will be increased (for example specifying pre-alpha: 1.6.0-alpha.1 -> 1.6.0-alpha.2 or, specifying pre-beta: 1.6.0-alpha.1 -> 1.6.0-beta.0)
- All other changes will increment the patch version.
- If the string "BREAKING CHANGE", "major" or the Attention pattern
- Push the bumped npm version in package.json back into the repo.
- Push a tag for the new version back into the repo.
Usage:
tag-prefix: Prefix that is used for the git tag (optional). Example:
- name: 'Automated Version Bump'
uses: 'phips28/gh-action-bump-version@master'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag-prefix: ''
skip-tag: The tag is not added to the git repository (optional). Example:
- name: 'Automated Version Bump'
uses: 'phips28/gh-action-bump-version@master'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
skip-tag: 'true'
default: Set a default version bump to use (optional - defaults to patch). Example:
- name: 'Automated Version Bump'
uses: 'phips28/gh-action-bump-version@master'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
default: prerelease
wording: Customize the messages that trigger the version bump. It must be a string, case sensitive, coma separated (optional). Example:
- name: 'Automated Version Bump'
uses: 'phips28/gh-action-bump-version@master'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
minor-wording: 'add,Adds,new'
major-wording: 'MAJOR,cut-major'
patch-wording: 'patch,fixes' # Providing patch-wording will override commits
# defaulting to a patch bump.
rc-wording: 'RELEASE,alpha'
PACKAGEJSON_DIR: Param to parse the location of the desired package.json (optional). Example:
- name: 'Automated Version Bump'
uses: 'phips28/gh-action-bump-version@master'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
PACKAGEJSON_DIR: 'frontend'