scaffoldly/Bump Versions, Manage Tags, and Create and Manage Releases
GitHub Action to Bump Versions, Manage Tags, and to Create and Manage Releases
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| action | The release action ('prerelease' or 'postrelease') | yes | — |
| version-file | The file that maintains the version (e.g. package.json, sly.json) | yes | — |
| repo-token | The GitHub token for this repo (https://docs.github.com/en/actions/reference/authentication-in-a-workflow#example-passing-github_token-as-an-input) | yes | — |
| major-tag | If set, will create/overwrite a tag representing the major release ('v1'). Only applicable during during postrelease | no | — |
| commit-message-prefix | If set, this prefix will be added to any commit messages | no | — |
| release-branch | If set, set the branch that version commits will be pushed to | no | — |
| tag-prefix | Prefix the version tag with a string (e.g. 'v') | no | — |
| dnt | If set, opt-out of usage analytics (https://docs.scaffold.ly/infrastructure/security/usage-analytics) | no | — |
Outputs
no outputs