add 'update_tag' option

This commit is contained in:
iTrooz 2024-07-22 23:31:31 +02:00
parent c062e08bd5
commit eb679c5bfa
No known key found for this signature in database
GPG key ID: 8B83F77667B1BC6A
5 changed files with 69 additions and 8 deletions

View file

@ -194,6 +194,7 @@ The following are optional as `step.with` keys
| `generate_release_notes` | Boolean | Whether to automatically generate the name and body for this release. If name is specified, the specified name will be used; otherwise, a name will be automatically generated. If body is specified, the body will be pre-pended to the automatically generated notes. See the [GitHub docs for this feature](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes) for more information |
| `append_body` | Boolean | Append to existing body instead of overwriting it |
| `make_latest` | String | Specifies whether this release should be set as the latest release for the repository. Drafts and prereleases cannot be set as latest. Can be `true`, `false`, or `legacy`. Uses GitHub api defaults if not provided |
| `update_tag` | Boolean | Update the tag of the release to the current commit. This will also update the release time. Default is false |
💡 When providing a `body` and `body_path` at the same time, `body_path` will be
attempted first, then falling back on `body` if the path can not be read from.