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
feat: provide inputs for releaser and manifest options in release-please 13.15 (#474)
* Synchronised action inputs with ReleaserConfig and ManifestOptions from release-please 13.15.0
* fix conflict from merge
* fix merge issue
* fix merge issue
Co-authored-by: Benjamin E. Coe <bencoe@google.com>
Co-authored-by: Jeff Ching <chingor@google.com>
Copy file name to clipboardExpand all lines: README.md
+44-21Lines changed: 44 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,27 +44,50 @@ Automate releases with Conventional Commit Messages.
44
44
45
45
## Configuration
46
46
47
-
| input | description |
48
-
|:---:|---|
49
-
| `token` | A GitHub secret token, the action defaults to using the special `secrets.GITHUB_TOKEN` |
50
-
| `release-type` | What type of project is this a release for? Reference [Release types supported](#release-types-supported); new types of releases can be [added here](https://github.com/googleapis/release-please/tree/main/src/strategies) |
51
-
| `package-name` | A name for the artifact releases are being created for (this might be the `name` field in a `setup.py` or `package.json`) |
52
-
| `bump-minor-pre-major` | Should breaking changes before 1.0.0 produce minor bumps? Default `false` |
53
-
| `bump-patch-for-minor-pre-major` | Should feat changes before 1.0.0 produce patch bumps instead of minor bumps? Default `false` |
54
-
| `path` | create a release from a path other than the repository's root |
55
-
| `monorepo-tags` | add prefix to tags and branches, allowing multiple libraries to be released from the same repository. |
56
-
| `changelog-types` | A JSON formatted String containing to override the outputted changelog sections |
57
-
| `version-file` | provide a path to a version file to increment (used by ruby releaser) |
58
-
| `extra-files` | add extra-files to bump using the [generic updater](https://github.com/googleapis/release-please/blob/main/docs/customizing.md#updating-arbitrary-files) |
59
-
| `fork` | Should the PR be created from a fork. Default `false`|
60
-
| `command` | release-please command to run, either `github-release`, or `release-pr`, `manifest`, `manifest-pr` (_defaults to running both_) |
61
-
| `default-branch` | branch to open pull release PR against (detected by default) |
62
-
| `pull-request-title-pattern` | title pattern used to make release PR, defaults to using `chore${scope}: release${component} ${version}`. |
| `github-api-url` | configure github API URL. Default `https://api.github.com` |
65
-
| `--signoff` | Add [`Signed-off-by`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) line at the end of the commit log message using the user and email provided. (format "Name \<email@example.com\>") |
| `token` | A GitHub secret token, the action defaults to using the special `secrets.GITHUB_TOKEN` |
50
+
| `release-type` | What type of project is this a release for? Reference [Release types supported](#release-types-supported); new types of releases can be [added here](https://github.com/googleapis/release-please/tree/main/src/strategies) |
51
+
| `package-name` | A name for the artifact releases are being created for (this might be the `name` field in a `setup.py` or `package.json`) |
52
+
| `bump-minor-pre-major` | Should breaking changes before 1.0.0 produce minor bumps? Default `false` |
53
+
| `bump-patch-for-minor-pre-major` | Should feat changes before 1.0.0 produce patch bumps instead of minor bumps? Default `false` |
54
+
| `path` | create a release from a path other than the repository's root |
55
+
| `monorepo-tags` | add prefix to tags and branches, allowing multiple libraries to be released from the same repository. |
56
+
| `changelog-types` | A JSON formatted String containing to override the outputted changelog sections |
57
+
| `version-file` | provide a path to a version file to increment (used by ruby releaser) |
58
+
| `extra-files` | add extra-files to bump using the [generic updater](https://github.com/googleapis/release-please/blob/main/docs/customizing.md#updating-arbitrary-files) |
59
+
| `fork` | Should the PR be created from a fork. Default `false` |
60
+
| `command` | release-please command to run, either `github-release`, or `release-pr`, `manifest`, `manifest-pr` (_defaults to running both_) |
61
+
| `default-branch` | branch to open pull release PR against (detected by default) |
62
+
| `pull-request-title-pattern` | title pattern used to make release PR, defaults to using `chore${scope}: release${component} ${version}`. |
| `github-api-url` | configure github API URL. Default `https://api.github.com` |
65
+
| `signoff` | Add [`Signed-off-by`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) line at the end of the commit log message using the user and email provided. (format "Name \<email@example.com\>") |
| `changelog-notes-type` | Strategy for building the [changelog contents](https://github.com/googleapis/release-please/blob/main/docs/customizing.md#changelog-types). Default `default`. Called `changelog-type` in release-please documentation. |
69
+
| `changelog-host` | Host for commit hyperlinks in the changelog. Default `https://github.com` |
70
+
| `versioning-strategy` | Override [method of determining SemVer version bumps based on commits](https://github.com/googleapis/release-please/blob/main/docs/customizing.md#versioning-strategies). Default `default` |
71
+
| `release-as` | manually set version to this value, ignoring conventional commits. Absence defaults to conventional commits derived next version. Once the release PR is merged you should either remove this or update it to a higher version. Otherwise subsequent `manifest-pr` runs will continue to use this version even though it was already set in the last release. |
| `prerelease` | If set, create releases that are pre-major or pre-release version marked as pre-release on Github. Defaults `false` |
74
+
| `component` | Name of the component used for branch naming and release tagging. Defaults to a normalized version based on the package name |
75
+
| `include-v-in-tag` | include "v" in tag versions. Default `true` |
76
+
| `tag-separator` | configures separator character used in release tag |
77
+
| `snapshot-labels` | sets java snapshot pull request labels other than `autorelease: snapshot` |
78
+
| `bootstrap-sha` | if this is the first time running `manifest-pr` on a repo this key will limit how far back (exclusive) to pull commits for conventional commit parsing, see (the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md] |
79
+
| `last-release-sha` | overrides the commit sha release-please will use from which to gather commits for the current release, see (the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md] |
80
+
| `always-link-local` | when using the `node-workspace` plugin, setting to false will only bump your local dependencies within the SemVer range, see (the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md] . Default `true`. |
81
+
| `separate-pull-requests` | create separate pull requests for each package instead of a single manifest release pull request, see (the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md]. Default `false`. |
82
+
| `plugins` | see https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#plugins |
83
+
| `labels` | list of labels to apply to the release pull requests, defaults to `autorelease: pending` |
84
+
| `release-labels` | set a pull request label other than `autorelease: tagged` |
85
+
| `skip-labeling` | if set, labels will not be applied to pull requests. Default `false`. |
86
+
| `sequential-calls` | issue GitHub API requests sequentially rather than concurrently, see (the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md]. Default `false` |
87
+
| `group-pull-request-title-pattern` | sets the manifest pull request title for when releasing multiple packages grouped together in the one pull request |
88
+
| `release-search-depth` | when searching for the latest release SHAs, only consider the last N releases |
89
+
| `commit-search-depth` | when fetching the list of commits to consider, only consider the last N commits |
90
+
68
91
69
92
### The `command` option
70
93
Some additional info regarding the `command` property.
0 commit comments