actions-marketplace-validations/NPM Publish Version
An action for publishing NPM packages with a specified version or against a given tag.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 11, 2022
- License
- None
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/matt-usurp_npm-publish@0f2749322fe388b2d3de2d93febf695e0070a99c # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| version | The version you wish to publish. This should be a semvar compliant version string with or without the "v" prefix. Optionally this can be a "git-ref" path where the final segment is a semver compliant version string. | yes | — |
| directory | The directory of the package that you wish to publish. This can be ignored if you are publishing the repository root. Ensure a "package.json" can be found in this directory. | no | — |
| tag | This is the "npm-dist-tag" mentioned in the official documentation. Ignore this value and it will default to "latest" as expected. Otherwise provide the development channel you wish this to be tagged as. | no | — |
| access | This is the "npm-access" mentioned in the official documentation. Ignore this value and it will default to "public" as expected. Otherwise provide the string "private" to make a private package. | no | — |
| silent | The action will silence the outputs of all the commands executed. Ignore this value and output will be printed. Otherwise provide a boolean truthy value. | no | — |
| execute | The publish command will be ran instead of the staging/dry-run mode by default. This is required to explicitly execute the commands as publishing can be messy otherwise. Otherwise provide a boolean truthy value. | no | — |
Outputs
| name | description |
|---|---|
| version | The version used to publish the package. This value has been stripped of any prefixes and is a raw semver string. |