jamesmgreene/Node Draft Releaser
Automatically publish an existing Draft Release when the "package.json" version changes
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| allow_unmatched_draft_tag | Should this be allowed to publish an existing Draft Release that is not slated to create a Tag matching the new version number? | — | true |
| allow_release_name_update | Should this Action be allowed to update the name of an existing Draft Release if its current name is a different valid SemVer version number? | — | true |
Outputs
| name | description |
|---|---|
| version | The new version number that was released |
| release_id | The ID of the Release |
| release_url | The URL to view the published Release page in the GitHub UI |