chlbri/npm-publish-action
GitHub Action for publishing packages to NPM with smart version checking
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| token | Authentication token to use with the configured registry | yes | — |
| registry | Registry URL to use | no | https://registry.npmjs.org/ |
| package | Path to a package directory, a package.json, or a packed .tgz to publish | no | — |
| tag | Distribution tag to publish to | no | latest |
| access | Whether the package should be publicly visible or restricted (public/restricted) | no | public |
| provenance | Run npm publish with the --provenance flag to add provenance statements | no | false |
| strategy | Publish strategy: "all" to publish all unique versions, "upgrade" for only semver upgrades | no | upgrade |
| ignore-scripts | Run npm publish with the --ignore-scripts flag as a security precaution | no | true |
| dry-run | Run npm publish with the --dry-run flag to prevent publication | no | false |
Outputs
| name | description |
|---|---|
| id | Package identifier of the release: ${name}@${version} or empty if no release |
| type | Semver release type, initial if first release, different if other change, or empty if no release |
| name | Name of the package |
| version | Version of the package |
| old-version | Previously published version on tag or empty if no previous version on tag |
| tag | Distribution tag the package was published to |
| access | Access level the package was published with, or default if scoped-package defaults were used |
| registry | Registry the package was published to |
| dry-run | Whether npm publish was run in dry run mode |