oss-actions/Auto Semver
Easily manage versioning for your repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| token | a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) or `$ {{ github.token }}`. This is used together with the `git` commandline to list commits and tags in your repository. | yes | — |
| repository | Which repository to autosemver for. This should normally be set to `$ {{ github.repository }}`. | yes | — |
| type | What type of increment to do on the previous version. Supported values are `major`, `minor` and `patch`. | yes | — |
| vprefix | Whether or not to include a `v` in the beginning of the version. | no | — |
Outputs
| name | description |
|---|---|
| version | The next version to tag. |
| minor_version | Same as `version` but with the `.<PATCH>` cut off. |
| major_version | Same as `version` but with the `.<MINOR>.<PATCH>` cut off. |
| previous_version | The highest and currently available semver tag in the repository. |
| previous_version_ref | The commit reference that the highest and currently available semver tag is referencing to. |