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
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,13 +58,26 @@ Create a [project access token](https://docs.gitlab.com/user/project/settings/pr
58
58
59
59
**Note**: When running with [`dryRun`](https://semantic-release.gitbook.io/semantic-release/usage/configuration#dryrun) only `read_repository` scope is required.
60
60
61
+
#### Using a CI Job Token
62
+
63
+
When running in a GitLab CI/CD environment, you can use the `CI_JOB_TOKEN` for authentication. To enable this, set the `useJobToken` option to `true` in your plugin configuration:
> **Important**: When `useJobToken` is enabled, comments on issues and merge requests are automatically disabled. This is due to the limited permissions of the `CI_JOB_TOKEN` which do not allow for these actions.
|`gitlabUrl`| The GitLab endpoint. |`GL_URL` or `GITLAB_URL` environment variable or CI provided environment variables if running on [GitLab CI/CD](https://docs.gitlab.com/ci/) or `https://gitlab.com`. |
88
101
|`gitlabApiPathPrefix`| The GitLab API prefix. |`GL_PREFIX` or `GITLAB_PREFIX` environment variable or CI provided environment variables if running on [GitLab CI/CD](https://docs.gitlab.com/ci/) or `/api/v4`. |
102
+
|`useJobToken`| Set to `true` to use the `CI_JOB_TOKEN` for authentication within a GitLab CI/CD environment. |`false`|
89
103
|`assets`| An array of files to upload to the release. See [assets](#assets). | - |
90
104
|`milestones`| An array of milestone titles to associate to the release. See [GitLab Release API](https://docs.gitlab.com/api/releases/#create-a-release). | - |
91
105
|`successComment`| The comment to add to each Issue and Merge Request resolved by the release. See [successComment](#successComment). |:tada: This issue has been resolved in version ${nextRelease.version} :tada:\n\nThe release is available on [GitLab release](gitlab_release_url)|
0 commit comments