| github-token | A github token with access to write tags and releases to the repository. | — | — |
| registry-token | An auth token with access to publish to the registry. If one is not provided, OIDC auth must be configured for the publish to work. | no | — |
| changelog-titles | A JSON encoded object, mapping the conventional commit type to the section title to use in the changelog for that type. These values will be merged into and override the default titles. (ex. `{ "feat": "New Features" }`) | — | — |
| disable-git-tagging | Disable setting and/or updating the git tags. | — | false |
| dry-run | Run the action without actually publishing the package, pushing git tags, or creating a GitHub release. | — | false |
| enable-github-release | Create a GitHub Release. | — | false |
| get-release-title-from-pr | Attempt to get the PR title from a PR associated to the git sha. If it is found, use the PR title as the release title. If not found, fall back to the release tag name. If the `release-title` has a truthy value, it will override this option. Note: The GITHUB_TOKEN requires `pull-requests: read` permissions. | — | false |
| git-tag-suffix | A value append to the git tags. | — | — |
| latest-tag-name | The tag used to track the latest commit on the release branch. | — | latest |
| major-types | A comma-separated list of conventional commit types that trigger a major version change. | — | — |
| minor-types | A comma-separated list of conventional commit types that trigger a minor version change. It defaults to `feat` | — | — |
| npmrc-content | Manually set the contents of the .npmrc file written to the `npmrc-path` location. | — | — |
| npmrc-path | A path to the `.npmrc` file. Defaults to `$HOME/.npmrc`. | — | — |
| package-directory | The path to the directory containing the package to be published. It must be a relative path, relative to the root of the repository. It defaults to the root of the repository. | — | — |
| prepend-version-to-release-title | Whether to prepend the release version to the release title. Note: this only applies when `get-release-title-from-pr` is `true`. | — | false |
| private | Whether to publish the package as a `private` package. | — | false |
| registry-url | The URL of the package registry to publish to. It defaults to npm's registry `registry.npmjs.org`. | — | — |
| release-title | The title to use for the GitHub release. If not set, or an empty string, the release tag name will be used. | — | — |
| scripts-package-directory | The path to a directory containing a package.json file which contains the project's scripts. Set this to use a custom `publish` script in the package.json file. It must be a relative path, relative to the root of the repository. It defaults to the value of the `package-directory` input. | — | — |
| version-override | The version to use for publishing the package instead of determining the version using conventional commits. | — | — |