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
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,7 @@ If you need to bypass the proxy for some hosts, configure the `NO_PROXY` environ
92
92
|`successCommentCondition`| Use this as condition, when to comment on issues or merge requests. See [successCommentCondition](#successCommentCondition). | - |
93
93
|`failComment`| The content of the issue created when a release fails. See [failComment](#failcomment). | Friendly message with links to **semantic-release** documentation and support, with the list of errors that caused the release to fail. |
94
94
|`failTitle`| The title of the issue created when a release fails. |`The automated release is failing 🚨`|
95
+
|`failCommentCondition`| Use this as condition, when to comment on or create an issues in case of failures. See [failCommentCondition](#failCommentCondition). | - |
95
96
|`labels`| The [labels](https://docs.gitlab.com/ee/user/project/labels.html#labels) to add to the issue created when a release fails. Set to `false` to not add any label. Labels should be comma-separated as described in the [official docs](https://docs.gitlab.com/ee/api/issues.html#new-issue), e.g. `"semantic-release,bot"`. |`semantic-release`|
96
97
|`assignee`| The [assignee](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#assignee) to add to the issue created when a release fails. | - |
97
98
@@ -188,6 +189,27 @@ The `failComment` `This release from branch ${branch.name} had failed due to the
188
189
> - Error message 1
189
190
> - Error message 2
190
191
192
+
#### failCommentCondition
193
+
194
+
The fail comment condition is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:
|`branch`|`Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done. |
199
+
|`lastRelease`|`Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release. |
200
+
|`nextRelease`|`Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done. |
201
+
|`commits`|`Array` of commit `Object`s with `hash`, `subject`, `body``message` and `author`. |
202
+
|`releases`|`Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`. |
203
+
|`issue`| A [GitLab API Issue object](https://docs.gitlab.com/ee/api/issues.html#single-issue) the comment will be posted to - only available if an open issue exists. |
204
+
205
+
##### failCommentCondition example
206
+
207
+
- do no create any comments at all: `"<% return false; %>"`
208
+
- to only comment on main branch: `"<% return branch.name === 'main' %>"`
209
+
- you can use labels to filter issues, i.e. to not comment if the issue is labeled with `wip`: `"<% return !issue.labels?.includes('wip') %>"`
210
+
211
+
> check the [GitLab API Merge Request object](https://docs.gitlab.com/ee/api/merge_requests.html#get-single-mr) or the [GitLab API Issue object](https://docs.gitlab.com/ee/api/issues.html#single-issue) for properties which can be used for the filter
212
+
191
213
## Compatibility
192
214
193
215
The latest version of this plugin is compatible with all currently-supported versions of GitLab, [which is the current major version and previous two major versions](https://about.gitlab.com/support/statement-of-support.html#version-support). This plugin is not guaranteed to work with unsupported versions of GitLab.
description: `## :rotating_light: The automated release from the \`main\` branch failed. :rotating_light:
332
+
333
+
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
334
+
335
+
You can find below the list of errors reported by **semantic-release**. Each one of them has to be resolved in order to automatically publish your package. I'm sure you can fix this 💪.
336
+
337
+
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
338
+
339
+
Once all the errors are resolved, **semantic-release** will release your package the next time you push a commit to the \`main\` branch. You can also manually restart the failed CI job that runs **semantic-release**.
340
+
341
+
If you are not sure how to resolve this, here are some links that can help you:
If those don't help, or if this issue is reporting something you think isn't right, you can always ask the humans behind **[semantic-release](https://github.com/semantic-release/semantic-release/issues/new)**.
347
+
348
+
---
349
+
350
+
### An error occured
351
+
352
+
Unfortunately this error doesn't have any additional information.
353
+
354
+
---
355
+
356
+
Good luck with your project ✨
357
+
358
+
Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package: :rocket:`,
0 commit comments