You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1
Original file line number
Diff line number
Diff line change
@@ -181,6 +181,7 @@ The following are optional as `step.with` keys
181
181
| `discussion_category_name` | String | If specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository. For more information, see ["Managing categories for discussions in your repository."](https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) |
182
182
| `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 |
183
183
| `append_body` | Boolean | Append to existing body instead of overwriting it |
184
+
| `make_latest` | Boolean | Whether to mark the release as latest or not. This defaults to true. |
184
185
185
186
💡 When providing a `body` and `body_path` at the same time, `body_path` will be
186
187
attempted first, then falling back on `body` if the path can not be read from.
0 commit comments