menduz/Deploy to NPM with oddish
Deploy your NPM package using oddish directly from GitHub
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| cwd | Working directory | no | — |
| provenance | Use npm provenance | no | true |
| main-branch-latest-tag | Use main branch build to release 'latest' dist-tags | no | false |
| always-auth | Set always-auth in npmrc | no | false |
| registry-url | Optional registry to set up for auth. Will set the registry in a project level .npmrc and .yarnrc file, and set up auth to read in from env.NODE_AUTH_TOKEN | no | https://registry.npmjs.org |
| access | 'restricted' or 'public' to set the scoped package visibility | no | "" |
| deterministic-snapshot | use runId instead of Time for the snapshot, to get deterministic snapshots | no | "" |
| only-update-versions | skips publishing, updates the version and commit in package.json | no | "" |
| gitlab-token | gitlab token to trigger pipelines | no | "" |
| gitlab-pipeline-url | gitlab pipeline URL | no | "" |
| s3-bucket | Target s3 bucket | no | — |
| s3-bucket-region | Target s3 bucket region | no | — |
| s3-bucket-key-prefix | Target s3 bucket key | no | — |
| scope | Optional scope for authenticating against scoped registries | no | — |
| custom-tag | Optional tag value to point instead of defining it with the git-tag or in function of current branch. When this value is set, `branch-to-custom-tag` has to be defined | no | "" |
| branch-to-custom-tag | Required when `custom-tag` is defined. Set the branch is going to publish to `custom-tag` | no | "" |
Outputs
| name | description |
|---|---|
| version | published version |
| latest | was the @latest tag published? |
| tags | published tags |