{"id":13553092,"url":"https://github.com/semantic-release/github","last_synced_at":"2025-04-14T20:42:55.832Z","repository":{"id":26880646,"uuid":"109930348","full_name":"semantic-release/github","owner":"semantic-release","description":":octocat:  semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues","archived":false,"fork":false,"pushed_at":"2025-04-08T19:50:22.000Z","size":3631,"stargazers_count":450,"open_issues_count":61,"forks_count":136,"subscribers_count":12,"default_branch":"master","last_synced_at":"2025-04-08T23:15:38.227Z","etag":null,"topics":["git","github","publish","release","semantic-release","version"],"latest_commit_sha":null,"homepage":"https://www.npmjs.com/package/@semantic-release/github","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/semantic-release.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-11-08T05:10:13.000Z","updated_at":"2025-04-06T03:18:54.000Z","dependencies_parsed_at":"2024-05-01T02:41:12.661Z","dependency_job_id":"0ba6ed05-fb45-4b2c-b623-86a8480d6880","html_url":"https://github.com/semantic-release/github","commit_stats":{"total_commits":742,"total_committers":42,"mean_commits":"17.666666666666668","dds":"0.39487870619946097","last_synced_commit":"012840384c7220d3c4235e670c45552d6ff6f8c5"},"previous_names":[],"tags_count":173,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/semantic-release%2Fgithub","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/semantic-release%2Fgithub/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/semantic-release%2Fgithub/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/semantic-release%2Fgithub/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/semantic-release","download_url":"https://codeload.github.com/semantic-release/github/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248960050,"owners_count":21189978,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["git","github","publish","release","semantic-release","version"],"created_at":"2024-08-01T12:02:17.163Z","updated_at":"2025-04-14T20:42:55.808Z","avatar_url":"https://github.com/semantic-release.png","language":"JavaScript","readme":"# @semantic-release/github\n\n[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a\n[GitHub release](https://help.github.com/articles/about-releases) and comment on released Pull Requests/Issues.\n\n[![Build Status](https://github.com/semantic-release/github/workflows/Test/badge.svg)](https://github.com/semantic-release/github/actions?query=workflow%3ATest+branch%3Amaster)\n\n[![npm latest version](https://img.shields.io/npm/v/@semantic-release/github/latest.svg)](https://www.npmjs.com/package/@semantic-release/github)\n[![npm next version](https://img.shields.io/npm/v/@semantic-release/github/next.svg)](https://www.npmjs.com/package/@semantic-release/github)\n[![npm beta version](https://img.shields.io/npm/v/@semantic-release/github/beta.svg)](https://www.npmjs.com/package/@semantic-release/github)\n\n| Step               | Description                                                                                                                                                                                                                              |\n| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `verifyConditions` | Verify the presence and the validity of the authentication (set via [environment variables](#environment-variables)) and the [assets](#assets) option configuration.                                                                     |\n| `publish`          | Publish a [GitHub release](https://help.github.com/articles/about-releases), optionally uploading file assets.                                                                                                                           |\n| `addChannel`       | Update a [GitHub release](https://help.github.com/articles/about-releases)'s `pre-release` field.                                                                                                                                        |\n| `success`          | Add a comment to each [GitHub Issue](https://help.github.com/articles/about-issues) or [Pull Request](https://help.github.com/articles/about-pull-requests) resolved by the release and close issues previously open by the `fail` step. |\n| `fail`             | Open or update a [GitHub Issue](https://help.github.com/articles/about-issues) with information about the errors that caused the release to fail.                                                                                        |\n\n## Install\n\n\u003e [!TIP]\n\u003e You do not need to directly depend on this package if you are using `semantic-release`.\n\u003e `semantic-release` already depends on this package, and defining your own direct dependency can result in conflicts when you update `semantic-release`.\n\n```bash\n$ npm install @semantic-release/github -D\n```\n\n## Usage\n\nThe plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):\n\n```json\n{\n  \"plugins\": [\n    \"@semantic-release/commit-analyzer\",\n    \"@semantic-release/release-notes-generator\",\n    [\n      \"@semantic-release/github\",\n      {\n        \"assets\": [\n          { \"path\": \"dist/asset.min.css\", \"label\": \"CSS distribution\" },\n          { \"path\": \"dist/asset.min.js\", \"label\": \"JS distribution\" }\n        ]\n      }\n    ]\n  ]\n}\n```\n\nWith this example [GitHub releases](https://help.github.com/articles/about-releases) will be published with the file `dist/asset.min.css` and `dist/asset.min.js`.\n\n## Configuration\n\n### GitHub authentication\n\nThe GitHub authentication configuration is **required** and can be set via [environment variables](#environment-variables).\n\nFollow the [Creating a personal access token for the command line](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) documentation to obtain an authentication token. The token has to be made available in your CI environment via the `GH_TOKEN` environment variable. The user associated with the token must have push permission to the repository.\n\nWhen creating the token, the **minimum required scopes** are:\n\n- [`repo`](https://github.com/settings/tokens/new?scopes=repo) for a private repository\n- [`public_repo`](https://github.com/settings/tokens/new?scopes=public_repo) for a public repository\n\n_Note on GitHub Actions:_ You can use the default token which is provided in the secret _GITHUB_TOKEN_. However releases done with this token will NOT trigger release events to start other workflows.\nIf you have actions that trigger on newly created releases, please use a generated token for that and store it in your repository's secrets (any other name than GITHUB_TOKEN is fine).\n\nWhen using the _GITHUB_TOKEN_, the **minimum required permissions** are:\n\n- `contents: write` to be able to publish a GitHub release\n- `issues: write` to be able to comment on released issues\n- `pull-requests: write` to be able to comment on released pull requests\n\n### Environment variables\n\n| Variable                       | Description                                                         |\n| ------------------------------ | ------------------------------------------------------------------- |\n| `GITHUB_TOKEN` or `GH_TOKEN`   | **Required.** The token used to authenticate with GitHub.           |\n| `GITHUB_URL` or `GH_URL`       | The GitHub server endpoint.                                         |\n| `GITHUB_PREFIX` or `GH_PREFIX` | The GitHub API prefix, relative to `GITHUB_URL`.                    |\n| `GITHUB_API_URL`               | The GitHub API endpoint. Note that this overwrites `GITHUB_PREFIX`. |\n\n### Options\n\n| Option                    | Description                                                                                                                                                                                            | Default                                                                                                                                              |\n| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `githubUrl`               | The GitHub server endpoint.                                                                                                                                                                            | `GH_URL` or `GITHUB_URL` environment variable.                                                                                                       |\n| `githubApiPathPrefix`     | The GitHub API prefix, relative to `githubUrl`.                                                                                                                                                        | `GH_PREFIX` or `GITHUB_PREFIX` environment variable.                                                                                                 |\n| `githubApiUrl`            | The GitHub API endpoint. Note that this overwrites `githubApiPathPrefix`.                                                                                                                              | `GITHUB_API_URL` environment variable.                                                                                                               |\n| `proxy`                   | The proxy to use to access the GitHub API. Set to `false` to disable usage of proxy. See [proxy](#proxy).                                                                                              | `HTTP_PROXY` environment variable.                                                                                                                   |\n| `assets`                  | An array of files to upload to the release. See [assets](#assets).                                                                                                                                     | -                                                                                                                                                    |\n| `successComment`          | The comment to add to each issue and pull request resolved by the release. Set to `false` to disable commenting on issues and pull requests. See [successComment](#successcomment).                    | `:tada: This issue has been resolved in version ${nextRelease.version} :tada:\\n\\nThe release is available on [GitHub release](\u003cgithub_release_url\u003e)` |\n| `successCommentCondition` | Use this as condition, when to comment on issues or pull requests. See [successCommentCondition](#successCommentCondition)                                                                             | -                                                                                                                                                    |\n| `failComment`             | The content of the issue created when a release fails. Set to `false` to disable opening an issue 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.              |\n| `failTitle`               | The title of the issue created when a release fails. Set to `false` to disable opening an issue when a release fails.                                                                                  | `The automated release is failing 🚨`                                                                                                                |\n| `failCommentCondition`    | Use this as condition, when to comment on or create an issues in case of failures. See [failCommentCondition](#failCommentCondition).                                                                  | -                                                                                                                                                    |\n| `labels`                  | The [labels](https://help.github.com/articles/about-labels) to add to the issue created when a release fails. Set to `false` to not add any label.                                                     | `['semantic-release']`                                                                                                                               |\n| `assignees`               | The [assignees](https://help.github.com/articles/assigning-issues-and-pull-requests-to-other-github-users) to add to the issue created when a release fails.                                           | -                                                                                                                                                    |\n| `releasedLabels`          | The [labels](https://help.github.com/articles/about-labels) to add to each issue and pull request resolved by the release. Set to `false` to not add any label. See [releasedLabels](#releasedlabels). | `['released\u003c%= nextRelease.channel ? \\` on @\\${nextRelease.channel}\\` : \"\" %\u003e']-                                                                     |\n| `addReleases`             | Will add release links to the GitHub Release. Can be `false`, `\"bottom\"` or `\"top\"`. See [addReleases](#addReleases).                                                                                  | `false`                                                                                                                                              |\n| `draftRelease`            | A boolean indicating if a GitHub Draft Release should be created instead of publishing an actual GitHub Release.                                                                                       | `false`                                                                                                                                              |\n| `releaseNameTemplate`     | A [Lodash template](https://lodash.com/docs#template) to customize the github release's name                                                                                                           | `\u003c%= nextverison.name %\u003e`                                                                                                                            |\n| `releaseBodyTemplate`     | A [Lodash template](https://lodash.com/docs#template) to customize the github release's body                                                                                                           | `\u003c%= nextverison.notes %\u003e`                                                                                                                           |\n| `discussionCategoryName`  | The category name in which to create a linked discussion to the release. Set to `false` to disable creating discussion for a release.                                                                  | `false`                                                                                                                                              |\n\n#### proxy\n\nCan be `false`, a proxy URL or an `Object` with the following properties:\n\n| Property      | Description                                                    | Default                              |\n| ------------- | -------------------------------------------------------------- | ------------------------------------ |\n| `host`        | **Required.** Proxy host to connect to.                        | -                                    |\n| `port`        | **Required.** Proxy port to connect to.                        | File name extracted from the `path`. |\n| `secureProxy` | If `true`, then use TLS to connect to the proxy.               | `false`                              |\n| `headers`     | Additional HTTP headers to be sent on the HTTP CONNECT method. | -                                    |\n\nSee [node-https-proxy-agent](https://github.com/TooTallNate/node-https-proxy-agent#new-httpsproxyagentobject-options) and [node-http-proxy-agent](https://github.com/TooTallNate/node-http-proxy-agent) for additional details.\n\n##### proxy examples\n\n`'http://168.63.76.32:3128'`: use the proxy running on host `168.63.76.32` and port `3128` for each GitHub API request.\n`{host: '168.63.76.32', port: 3128, headers: {Foo: 'bar'}}`: use the proxy running on host `168.63.76.32` and port `3128` for each GitHub API request, setting the `Foo` header value to `bar`.\n\n#### assets\n\nCan be a [glob](https://github.com/isaacs/node-glob#glob-primer) or and `Array` of\n[globs](https://github.com/isaacs/node-glob#glob-primer) and `Object`s with the following properties:\n\n| Property | Description                                                                                              | Default                              |\n| -------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------ |\n| `path`   | **Required.** A [glob](https://github.com/isaacs/node-glob#glob-primer) to identify the files to upload. | -                                    |\n| `name`   | The name of the downloadable file on the GitHub release.                                                 | File name extracted from the `path`. |\n| `label`  | Short description of the file displayed on the GitHub release.                                           | -                                    |\n\nEach entry in the `assets` `Array` is globbed individually. A [glob](https://github.com/isaacs/node-glob#glob-primer)\ncan be a `String` (`\"dist/**/*.js\"` or `\"dist/mylib.js\"`) or an `Array` of `String`s that will be globbed together\n(`[\"dist/**\", \"!**/*.css\"]`).\n\nIf a directory is configured, all the files under this directory and its children will be included.\n\nThe `name` and `label` for each assets are generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter     | Description                                                                         |\n| ------------- | ----------------------------------------------------------------------------------- |\n| `branch`      | The branch from which the release is done.                                          |\n| `lastRelease` | `Object` with `version`, `gitTag` and `gitHead` of the last release.                |\n| `nextRelease` | `Object` with `version`, `gitTag`, `gitHead` and `notes` of the release being done. |\n| `commits`     | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`.  |\n\n**Note**: If a file has a match in `assets` it will be included even if it also has a match in `.gitignore`.\n\n##### assets examples\n\n`'dist/*.js'`: include all the `js` files in the `dist` directory, but not in its sub-directories.\n\n`[['dist', '!**/*.css']]`: include all the files in the `dist` directory and its sub-directories excluding the `css`\nfiles.\n\n`[{path: 'dist/MyLibrary.js', label: 'MyLibrary JS distribution'}, {path: 'dist/MyLibrary.css', label: 'MyLibrary CSS distribution'}]`: include the `dist/MyLibrary.js` and `dist/MyLibrary.css` files, and label them `MyLibrary JS distribution` and `MyLibrary CSS distribution` in the GitHub release.\n\n`[['dist/**/*.{js,css}', '!**/*.min.*'], {path: 'build/MyLibrary.zip', label: 'MyLibrary'}]`: include all the `js` and\n`css` files in the `dist` directory and its sub-directories excluding the minified version, plus the\n`build/MyLibrary.zip` file and label it `MyLibrary` in the GitHub release.\n\n`[{path: 'dist/MyLibrary.js', name: 'MyLibrary-${nextRelease.gitTag}.js', label: 'MyLibrary JS (${nextRelease.gitTag}) distribution'}]`: include the file `dist/MyLibrary.js` and upload it to the GitHub release with name `MyLibrary-v1.0.0.js` and label `MyLibrary JS (v1.0.0) distribution` which will generate the link:\n\n\u003e `[MyLibrary JS (v1.0.0) distribution](MyLibrary-v1.0.0.js)`\n\n#### successComment\n\nThe message for the issue comments is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter     | Description                                                                                                                                                                                                                                                                                                                                        |\n| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `branch`      | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done.                                                                                                                                                                                                                         |\n| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release.                                                                                                                                                                                                                                                                    |\n| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done.                                                                                                                                                                                                                                                     |\n| `commits`     | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`.                                                                                                                                                                                                                                                                 |\n| `releases`    | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`.                                                                                                                                                                                                                                  |\n| `issue`       | A [GitHub API pull request object](https://developer.github.com/v3/search/#search-issues) for pull requests related to a commit, or [GitHub API issue object](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#get-an-issue) for issues resolved via [keywords](https://help.github.com/articles/closing-issues-using-keywords) |\n\n##### successComment example\n\nThe `successComment` `This ${issue.pull_request ? 'pull request' : 'issue'} is included in version ${nextRelease.version}` will generate the comment:\n\n\u003e This pull request is included in version 1.0.0\n\n#### successCommentCondition\n\nThe message for the issue comments is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter     | Description                                                                                                                                                    |\n| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `branch`      | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done.                                     |\n| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release.                                                                                |\n| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done.                                                                 |\n| `commits`     | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`.                                                                             |\n| `releases`    | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`.                                              |\n| `issue`       | A [GitHub API Pull Request object](https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#get-a-pull-request) for pull requests related to a commit |\n\n##### successCommentCondition example\n\n- do not create any comments at all: set to `false` or templating: `\"\u003c% return false; %\u003e\"`\n- to only comment on issues: `\"\u003c% return !issue.pull_request; %\u003e\"`\n- to only comment on pull requests: `\"\u003c% return issue.pull_request; %\u003e\"`\n- to avoid comment on PRs or issues created by Bots: `\"\u003c% return issue.user.type !== 'Bot'; %\u003e\"`\n- you can use labels to filter issues: `\"\u003c% return issue.labels?.some((label) =\u003e { return label.name === ('semantic-release-relevant'); }); %\u003e\"`\n\n\u003e check the [GitHub API issue object](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#get-an-issue) for properties which can be used for the filter\n\n#### failComment\n\nThe message for the issue content is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter | Description                                                                                                                                                                                                                                                                                                            |\n| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `branch`  | The branch from which the release had failed.                                                                                                                                                                                                                                                                          |\n| `errors`  | An `Array` of [SemanticReleaseError](https://github.com/semantic-release/error). Each error has the `message`, `code`, `pluginName` and `details` properties.\u003cbr\u003e`pluginName` contains the package name of the plugin that threw the error.\u003cbr\u003e`details` contains a information about the error formatted in markdown. |\n\n##### failComment example\n\nThe `failComment` `This release from branch ${branch.name} had failed due to the following errors:\\n- ${errors.map(err =\u003e err.message).join('\\\\n- ')}` will generate the comment:\n\n\u003e This release from branch master had failed due to the following errors:\n\u003e\n\u003e - Error message 1\n\u003e - Error message 2\n\n#### failCommentCondition\n\nThe message for the issue content is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter     | Description                                                                                                                                                                                                                                                                                                                                                                       |\n| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `branch`      | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done.                                                                                                                                                                                                                                                        |\n| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release.                                                                                                                                                                                                                                                                                                   |\n| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done.                                                                                                                                                                                                                                                                                    |\n| `commits`     | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`.                                                                                                                                                                                                                                                                                                |\n| `releases`    | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`.                                                                                                                                                                                                                                                                 |\n| `issue`       | A [GitHub API pull request object](https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#get-a-pull-request) for pull requests related to a commit, or [GitHub API issue object](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#get-an-issue) for issues resolved via [keywords](https://help.github.com/articles/closing-issues-using-keywords) |\n\n##### failCommentCondition example\n\n- do not create any comments at all: set to `false` or templating: `\"\u003c% return false; %\u003e\"`\n- to only comment on main branch: `\"\u003c% return branch.name === 'main' %\u003e\"`\n- you can use labels to filter issues, i.e. to not comment if the issue is labeled with `wip`: `\"\u003c% return !issue.labels?.includes('wip') %\u003e\"`\n\n\u003e check the [GitHub API Pull Request Object](https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#get-a-pull-request) for properties which can be used for the filter\n\n#### releasedLabels\n\nEach label name is generated with [Lodash template](https://lodash.com/docs#template). The following variables are available:\n\n| Parameter     | Description                                                                                                                                                                                                                                                                                                                                        |\n| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `branch`      | `Object` with `name`, `type`, `channel`, `range` and `prerelease` properties of the branch from which the release is done.                                                                                                                                                                                                                         |\n| `lastRelease` | `Object` with `version`, `channel`, `gitTag` and `gitHead` of the last release.                                                                                                                                                                                                                                                                    |\n| `nextRelease` | `Object` with `version`, `channel`, `gitTag`, `gitHead` and `notes` of the release being done.                                                                                                                                                                                                                                                     |\n| `commits`     | `Array` of commit `Object`s with `hash`, `subject`, `body` `message` and `author`.                                                                                                                                                                                                                                                                 |\n| `releases`    | `Array` with a release `Object`s for each release published, with optional release data such as `name` and `url`.                                                                                                                                                                                                                                  |\n| `issue`       | A [GitHub API pull request object](https://developer.github.com/v3/search/#search-issues) for pull requests related to a commit, or [GitHub API issue object](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#get-an-issue) for issues resolved via [keywords](https://help.github.com/articles/closing-issues-using-keywords) |\n\n##### releasedLabels example\n\nThe `releasedLabels` ``['released\u003c%= nextRelease.channel ? ` on @\\${nextRelease.channel}` : \"\" %\u003e from \u003c%= branch.name %\u003e']`` will generate the label:\n\n\u003e released on @next from branch next\n\n#### addReleases\n\nAdd links to other releases to the GitHub release body.\n\nValid values for this option are `false`, `\"top\"` or `\"bottom\"`.\n\n##### addReleases example\n\nSee [The introducing PR](https://github.com/semantic-release/github/pull/282) for an example on how it will look.\n","funding_links":[],"categories":["JavaScript","github"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsemantic-release%2Fgithub","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsemantic-release%2Fgithub","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsemantic-release%2Fgithub/lists"}