actions-marketplace-validations/NPM Publisher
Fast, easy publishing to NPM
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| token | The NPM access token to use when publishing | yes | — |
| registry | The NPM registry URL to use | no | https://registry.npmjs.org/ |
| package | The path of your package.json file | no | package.json |
| tag | The tag to publish to. This allows people to install the package using "npm install <package-name>@<tag>". | no | latest |
| access | Determines whether the published package should be publicly visible, or restricted to members of your NPM organization. This only applies to scoped packages. | no | — |
| dry-run | If true, run with the --dry-run flag | no | false |
| check-version | Only publish if the version in package.json differs from the latest on NPM | no | true |
| greater-version-only | Only publish to NPM if the version number in package.json is greater than the latest on NPM | no | false |
Outputs
| name | description |
|---|---|
| type | The type of version change that occurred ("none", "major", "minor", "patch", etc.) |
| version | The version that was published |
| old-version | The version number that was previously published to NPM |