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: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
## 0.1.14
2
+
3
+
- provides an new workflow input option `generate_release_notes` which when set to true will automatically generate release notes for you based on GitHub activity [#179](https://github.com/softprops/action-gh-release/pull/179). Please see the [GitHub docs for this feature](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes) for more information
4
+
1
5
## 0.1.13
2
6
3
7
- fix issue with multiple runs concatenating release bodies [#145](https://github.com/softprops/action-gh-release/pull/145)
| `body` | String | Text communicating notable changes in this release |
171
-
| `body_path` | String | Path to load text communicating notable changes in this release |
172
-
| `draft` | Boolean | Indicator of whether or not this release is a draft |
173
-
| `prerelease` | Boolean | Indicator of whether or not is a prerelease |
174
-
| `files` | String | Newline-delimited globs of paths to assets to upload for release |
175
-
| `name` | String | Name of the release. defaults to tag name |
176
-
| `tag_name` | String | Name of a tag. defaults to `github.ref` |
177
-
| `fail_on_unmatched_files` | Boolean | Indicator of whether to fail if any of the `files` globs match nothing |
178
-
| `repository` | String | Name of a target repository in `<owner>/<repo>` format. Defaults to GITHUB_REPOSITORY env variable |
179
-
| `target_commitish` | String | Commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. |
180
-
| `token` | String | Secret GitHub Personal Access Token. Defaults to `${{ github.token }}` |
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
-
| `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. |
| `body` | String | Text communicating notable changes in this release |
171
+
| `body_path` | String | Path to load text communicating notable changes in this release |
172
+
| `draft` | Boolean | Indicator of whether or not this release is a draft |
173
+
| `prerelease` | Boolean | Indicator of whether or not is a prerelease |
174
+
| `files` | String | Newline-delimited globs of paths to assets to upload for release |
175
+
| `name` | String | Name of the release. defaults to tag name |
176
+
| `tag_name` | String | Name of a tag. defaults to `github.ref` |
177
+
| `fail_on_unmatched_files` | Boolean | Indicator of whether to fail if any of the `files` globs match nothing |
178
+
| `repository` | String | Name of a target repository in `<owner>/<repo>` format. Defaults to GITHUB_REPOSITORY env variable |
179
+
| `target_commitish` | String | Commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. |
180
+
| `token` | String | Secret GitHub Personal Access Token. Defaults to `${{ github.token }}` |
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
+
| `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
184
184
💡 When providing a `body` and `body_path` at the same time, `body_path` will be
185
185
attempted first, then falling back on `body` if the path can not be read from.
0 commit comments