README.md

July 14, 2026 ยท View on GitHub

Version Bumper Action

:package::rocket: Spice up your release workflows with automated version bumps! :rocket::package:

About

The Version Bumper Action uses the version bumper tool to figure out the next semantic version bump based on conventional commits, or plain instructions.

Upgrading from version 1 to 2? Click here.

Successful upgrades examples: alexa-skills-tester, github-viewer-stats, auto-me-bot, tomfi-archetypes, shabbat-api,

Version 3 introduced breaking changes

  • The action was rebuilt using Node.js.
  • Changes in the action flags:
    • changelog was removed.
    • preset was removed.
    • folder was changed to path. It's worth mentioning the folder/path requires a full path and not a folder relative to the workspace. (folder will eventually be removed).
    • bumpoverride was changed to bump (bumpoverride will eventually be removed).

Usage example

- uses: actions/checkout@v2
  with:
    # fetch-depth 0 will check out all the commits and tags needed for the bumper
    fetch-depth: 0

- id: bumper
  uses: tomerfi/version-bumper-action@2.0.9

# assuming previous tag was 1.2.4 and feat-type commits were made, this will print 1.3.0.
- run: echo ${{ steps.bumper.outputs.next }}

Inputs

KeyDescriptionDefault value
sourceSource for the bump, any semver string or 'git' to fetch from tagsgit
bumpTarget bump, 'major', 'minor', 'patch', 'auto'. An 'auto' bump only works with a 'git' sourceauto
labelDevelopment iteration build label-dev
pathWhen source is 'git', set repository path${{ github.workspace }}

Outputs

KeyDescriptionExample
currentThe original version1.2.3
bumpThe bump performedpatch
nextThe next version1.2.4
devThe next development iteration version1.2.5-dev
major_partThe major part of the next version1
minor_partThe minor part of the next version2
patch_partThe patch part of the next version4
dev_patch_partThe patch part of the development iteration5-dev
bump_objectThe original object returned from the version bumper tool