actions-marketplace-validations/Gradle & Maven Version Bump
A simple GitHub Actions to bump the version of Gradle & Maven projects with extended functionality for automatic versioning.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Mar 12, 2025
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/plugily-projects_version-bump-action@6c7d91e91e6d5789c93f57a07491ac3cc16938e5 # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | A GitHub auth token to be able to create the pull request | yes | — |
| git-email | The email address used to create the version bump commit with. | yes | 41898282+version-bump[github-action]@users.noreply.github.com |
| git-username | The name to use for the version bump commit. e.g. github.actor | yes | version-bump[github-action] |
| git-committer | Who should be the committer? defined git [BOT] or last committer [USER] | yes | BOT |
| commit-skip | Skip this whole action when some phrase is on the commit | yes | [SKIP BUMP] |
| auto-version-bump | Should we bump the version on every commit? | yes | false |
| auto-version-bump-splitter | Version splitter for auto bump | yes | - |
| auto-version-bump-suffix | Version suffix for auto bump | yes | SNAPSHOT |
| auto-version-bump-higher | Should after the suffix a number bumped? | yes | true |
| auto-version-bump-release | Should on a automatic bump a tag and release created? | yes | false |
| auto-version-bump-mode | Mode for auto version, could be major, minor, patch or auto. Default is auto. | yes | auto |
Outputs
| name | description |
|---|---|
| version | The current version (whether updated or not) |
| before-version | The version before running this github action |
| bumped | If version got bumped (true/false) |