| action | The action to perform. Available actions are "bump" (default), "overwrite" and "nothing". | no | bump |
| level | The level of the SemVer to bump. | no | patch |
| overwrite | Value of the new version. Honored only if `action` is set to "overwrite". | no | "" |
| first-version | The first version to consider in case there are no pre-existing versions. | no | 1.0.0 |
| dry-run | If true, all sensitive operations will be mocked. | no | true |
| version-source | The source of where the current version is stored. It can be "semver-tags" (default), "file" or "value". | no | semver-tags |
| version-source-tags-semver-pattern | The pattern to filter the tags to only get the semver ones. It is honored only if `version-source` is set to "semver-tags". | no | ^v?\d+\.\d+\.\d+([_.-][a-zA-Z0-9_.+-]+)?$ |
| version-source-file | File where the current version is stored. It is required to set if `version-source` is set to "file". | no | "" |
| version-source-value | Value of the current version. It is required to set if `version-source` is set to "value". | no | "" |
| update-package-json | If true, the package.json and package-lock.json files will be updated to set the new version. If no such files exist, it will be ignored. | no | true |
| package-json-path | Path to the package.json path. Its lock file will be assumed to be in the same directory. | no | package.json |
| git-commit-changes | If true, and that there are changes in the repositories (after updating the package.json file or caused by the drop-in scripts), the action will create a new commit from the changes. Note that the commit will be performed in the current branch. | no | false |
| git-commit-title | The commit title. You can use the placeholder `%s` to specify the new version. | no | chore: bump version |
| git-commit-description | The commit description. You can use the placeholder `%s` to specify the new version. | no | - %s created from $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID
- [skip ci]
|
| git-commit-add-paths | The paths to add to the git index, separated by a white-space. | no | . |
| git-commit-skip-hooks | If true, the git hooks will be ignored when committing. | no | false |
| git-commit-push | If true, the created commit will be pushed to the remote branch. | no | true |
| create-git-tag | If true, the project will be tagged with the new version. | no | false |
| git-tag-force-creation | If true, the git tag creation will be forced, meaning that any existing tag with the same name will be removed. This is a destructive operation! | no | false |
| git-tag-format | If `git-tag` is true, you can specify here the format of the tag, with `%s` being the placeholder holding the new version value. | no | v%s |
| git-tag-message | If `git-tag` is true, you can specify here the message of the tag, with `%s` being the placeholder holding the new version value. | no | %s
Created from $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID
|
| git-tag-push | If true, the created tag will be pushed to the origin. | no | true |
| create-github-release | If true, a new GitHub Release will be created with the new tag. Ignored if `create-git-tag` is false. | no | false |
| github-release-force-creation | If true, the action will first search if a GitHub Release associated with the same tag exists, and if it does, it will remove it before creating the new GitHub Release. This is a destructive operation! | no | false |
| github-release-generate-notes | If true, the new GitHub Release name and description will be generated automatically using the GitHub REST API endpoint `repos/OWNER/REPO/releases/generate-notes`. Setting `github-release-name` or `github-release-body` with this parameter set to true will override the automatically-generated content. Fore more information please refer to: https://docs.github.com/en/rest/releases/releases?apiVersion=2026-03-10#generate-release-notes-content-for-a-release | no | true |
| github-release-generate-notes-previous-tag-name | The previous tag name to generate the release notes automatically and compare the versions. | no | "" |
| github-release-generate-notes-configuration-file-path | Path to the release note generator configuration file. Fore more information, please refer to: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes | no | "" |
| github-release-name | The name of the GitHub Release. If `github-release-generate-notes` is set to true, then this parameter will override the automatically generated content. | no | "" |
| github-release-body | The body of the GitHub Release. If `github-release-generate-notes` is set to true, then this parameter will override the automatically generated content. | no | "" |
| github-release-draft | If true, the new GitHub Release will be created as a draft. | no | false |
| github-release-prerelease | If true, the new GitHub Release will be created as a pre-release. | no | false |
| github-release-discussion-category-name | If set, the new GitHub Release will be associated to the given discussion category name. | no | "" |
| github-release-make-latest | If true, the new GitHub Release will be marked as the latest release. | no | true |
| github-release-assets | Semicolon-separated list of globstar patterns for uploading files to the GitHub Release. | no | "" |
| drop-in-scripts | If true, the action will execute any drop-in scripts found in the drop-in directory. | no | true |
| drop-in-dir | The drop-in directory. Note that it must NOT contain any scripts directly, only sub-directories representing the steps of execution. | no | semver-action.d/ |
| drop-in-timeout | Timeout for each drop-in script execution. | no | "" |
| drop-in-script-check-exit-code | If true and one of the drop-in script returns a non-zero exit code, the action will fail. | no | true |
| pass-github-token-to-drop-in-scripts | If true, the given value of `github-token` will be passed to the drop-in scripts. | no | false |
| write-job-summary | If true, the action will write a summary to the job to indicate what actions have been performed. | no | false |
| github-base-api-url | The base API URL of the GitHub instance. | no | https://api.github.com/ |
| github-token | Optional GitHub token to use when sending requests to the GitHub REST API. If none is specified, the default `GITHUB_TOKEN` will be used. | no | "" |
| github-owner-repo | The current repository name formatted as "owner/repo". If not specified, it will default to `GITHUB_REPOSITORY`. | no | "" |