semantic-release/github

:octocat: semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues

@semantic-release/github

semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues.

Step	Description
verifyConditions	Verify the presence and the validity of the authentication (set via environment variables) and the assets option configuration.
publish	Publish a GitHub release, optionally uploading file assets.
addChannel	Update a GitHub release's pre-release field.
success	Add a comment to each GitHub Issue or Pull Request resolved by the release and close issues previously open by the fail step.
fail	Open or update a GitHub Issue with information about the errors that caused the release to fail.

Install

$ npm install @semantic-release/github -D

Usage

The plugin can be configured in the semantic-release configuration file:

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    [
      "@semantic-release/github",
      {
        "assets": [
          { "path": "dist/asset.min.css", "label": "CSS distribution" },
          { "path": "dist/asset.min.js", "label": "JS distribution" }
        ]
      }
    ]
  ]
}

With this example GitHub releases will be published with the file dist/asset.min.css and dist/asset.min.js.

Configuration

GitHub authentication

The GitHub authentication configuration is required and can be set via environment variables.

Follow the 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.

When creating the token, the minimum required scopes are:

• repo for a private repository
• public_repo for a public repository

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. If 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).

When using the GITHUB_TOKEN, the minimum required permissions are:

• contents: write to be able to publish a GitHub release
• issues: write to be able to comment on released issues
• pull-requests: write to be able to comment on released pull requests

Environment variables

Variable	Description
GH_TOKEN or GITHUB_TOKEN	Required. The token used to authenticate with GitHub.
GITHUB_API_URL or GH_URL or GITHUB_URL	The GitHub Enterprise endpoint.
GH_PREFIX or GITHUB_PREFIX	The GitHub Enterprise API prefix.

Options

Option	Description	Default
githubUrl	The GitHub Enterprise endpoint.	GH_URL or GITHUB_URL environment variable.
githubApiPathPrefix	The GitHub Enterprise API prefix.	GH_PREFIX or GITHUB_PREFIX environment variable.
proxy	The proxy to use to access the GitHub API. Set to false to disable usage of proxy. See proxy.	HTTP_PROXY environment variable.
assets	An array of files to upload to the release. See assets.	-
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.	:tada: This issue has been resolved in version ${nextRelease.version} :tada:\n\nThe release is available on [GitHub release](<github_release_url>)
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.	Friendly message with links to semantic-release documentation and support, with the list of errors that caused the release to fail.
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 🚨
labels	The labels to add to the issue created when a release fails. Set to false to not add any label.	['semantic-release']
assignees	The assignees to add to the issue created when a release fails.	-
releasedLabels	The labels to add to each issue and pull request resolved by the release. Set to false to not add any label. See releasedLabels.	['released<%= nextRelease.channel ? \ on @${nextRelease.channel}` : "" %>']-
addReleases	Will add release links to the GitHub Release. Can be false, "bottom" or "top". See addReleases.	false
draftRelease	A boolean indicating if a GitHub Draft Release should be created instead of publishing an actual GitHub Release.	false
releaseNameTemplate	A Lodash template to customize the github release's name	<%= nextverison.name %>
releaseBodyTemplate	A Lodash template to customize the github release's body	<%= nextverison.notes %>
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

proxy

Can be false, a proxy URL or an Object with the following properties:

Property	Description	Default
host	Required. Proxy host to connect to.	-
port	Required. Proxy port to connect to.	File name extracted from the path.
secureProxy	If true, then use TLS to connect to the proxy.	false
headers	Additional HTTP headers to be sent on the HTTP CONNECT method.	-

See node-https-proxy-agent and node-http-proxy-agent for additional details.

proxy examples

'http://168.63.76.32:3128': use the proxy running on host 168.63.76.32 and port 3128 for each GitHub API request. {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.

assets

Can be a glob or and Array of globs and Objects with the following properties:

Property	Description	Default
path	Required. A glob to identify the files to upload.	-
name	The name of the downloadable file on the GitHub release.	File name extracted from the path.
label	Short description of the file displayed on the GitHub release.	-

Each entry in the assets Array is globbed individually. A glob can be a String ("dist/**/*.js" or "dist/mylib.js") or an Array of Strings that will be globbed together (["dist/**", "!**/*.css"]).

If a directory is configured, all the files under this directory and its children will be included.

The name and label for each assets are generated with Lodash template. The following variables are available:

Parameter	Description
branch	The branch from which the release is done.
lastRelease	Object with version, gitTag and gitHead of the last release.
nextRelease	Object with version, gitTag, gitHead and notes of the release being done.
commits	Array of commit Objects with hash, subject, body message and author.

Note: If a file has a match in assets it will be included even if it also has a match in .gitignore.

assets examples

'dist/*.js': include all the js files in the dist directory, but not in its sub-directories.

[['dist', '!**/*.css']]: include all the files in the dist directory and its sub-directories excluding the css files.

[{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.

[['dist/**/*.{js,css}', '!**/*.min.*'], {path: 'build/MyLibrary.zip', label: 'MyLibrary'}]: include all the js and css files in the dist directory and its sub-directories excluding the minified version, plus the build/MyLibrary.zip file and label it MyLibrary in the GitHub release.

[{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:

[MyLibrary JS (v1.0.0) distribution](MyLibrary-v1.0.0.js)

successComment

The message for the issue comments is generated with Lodash template. The following variables are available:

Parameter	Description
branch	Object with name, type, channel, range and prerelease properties of the branch from which the release is done.
lastRelease	Object with version, channel, gitTag and gitHead of the last release.
nextRelease	Object with version, channel, gitTag, gitHead and notes of the release being done.
commits	Array of commit Objects with hash, subject, body message and author.
releases	Array with a release Objects for each release published, with optional release data such as name and url.
issue	A GitHub API pull request object for pull requests related to a commit, or an Object with the number property for issues resolved via keywords

successComment example

The successComment This ${issue.pull_request ? 'pull request' : 'issue'} is included in version ${nextRelease.version} will generate the comment:

This pull request is included in version 1.0.0

failComment

The message for the issue content is generated with Lodash template. The following variables are available:

Parameter	Description
branch	The branch from which the release had failed.
errors	An Array of SemanticReleaseError. Each error has the message, code, pluginName and details properties. pluginName contains the package name of the plugin that threw the error. details contains a information about the error formatted in markdown.

failComment example

The failComment This release from branch ${branch.name} had failed due to the following errors:\n- ${errors.map(err => err.message).join('\\n- ')} will generate the comment:

This release from branch master had failed due to the following errors:

• Error message 1
• Error message 2

releasedLabels

Each label name is generated with Lodash template. The following variables are available:

Parameter	Description
branch	Object with name, type, channel, range and prerelease properties of the branch from which the release is done.
lastRelease	Object with version, channel, gitTag and gitHead of the last release.
nextRelease	Object with version, channel, gitTag, gitHead and notes of the release being done.
commits	Array of commit Objects with hash, subject, body message and author.
releases	Array with a release Objects for each release published, with optional release data such as name and url.
issue	A GitHub API pull request object for pull requests related to a commit, or an Object with the number property for issues resolved via keywords

releasedLabels example

The releasedLabels ['released<%= nextRelease.channel ? ` on @\${nextRelease.channel}` : "" %> from <%= branch.name %>'] will generate the label:

released on @next from branch next

addReleases

Add links to other releases to the GitHub release body.

Valid values for this option are false, "top" or "bottom".

addReleases example

See The introducing PR for an example on how it will look.

github's Issues

How to configure protected release branch

We are using @semantic-release/github and we would like to know the recommended configuration to work with protection:

Our release branch is master,

So far we did try to protect using:

  body='{
    "required_status_checks": {
      "strict":true,
      "contexts": [
        "continuous-integration/travis-ci"
      ]
    },
    "enforce_admins": true,
    "required_pull_request_reviews": null,
    "restrictions": {
        "users": [
          "kopax"
        ],
        "teams": [
          "developers"
        ]
    }
  }'

  curl -sS -L -X PUT \
    -H "Authorization: token ${GH_TOKEN:-$GITHUB_TOKEN}" \
    -H "Accept: application/vnd.github.luke-cage-preview+json" \
    "https://api.github.com/repos/${scope}/${name}/branches/dev/protection" \
  --compressed \
  --data-binary "$body"
  curl -sS -L -X PUT \
    -H "Authorization: token ${GH_TOKEN:-$GITHUB_TOKEN}" \
    -H "Accept: application/vnd.github.luke-cage-preview+json" \
    "https://api.github.com/repos/${scope}/${name}/branches/master/protection" \
  --compressed \
  --data-binary "$body"

We get the following error:

{ Error: Command failed: git push --tags https://[secure]@github.com/yeutech-lab/accept-dot-path.git HEAD:master
remote: error: GH006: Protected branch update failed for refs/heads/master.        
remote: error: Required status check "continuous-integration/travis-ci" is expected.        
To https://github.com/yeutech-lab/accept-dot-path.git
 ! [remote rejected] HEAD -> master (protected branch hook declined)

I assume we should disable travis ci check, but that seems a bit odd decision, how do you users of semantic-release recommand to configure the protection on GitHub?

Release fails when adding "release" labels. Error 422.

Hello,

I'm not sure which version introduced this issue, but I know it happens as far back as 5.2.1 for me (It happened on 5.2.5 and 5.2.6).

I'm seeing the following only when PRs are merged:

[14:14:30] [semantic-release] [@semantic-release/github] › ℹ  Added comment to issue #538: https://github.enterprise.com/ORG/plugin-cli/pull/538#issuecomment-518258
[14:14:33] [semantic-release] [@semantic-release/github] › ℹ  Added comment to issue #539: https://github.enterprise.com/ORG/plugin-cli/pull/539#issuecomment-518259
[14:14:36] [semantic-release] [@semantic-release/github] › ℹ  Added comment to issue #541: https://github.enterprise.com/ORG/plugin-cli/pull/541#issuecomment-518260
[14:15:06] [semantic-release] [@semantic-release/github] › ✖  Failed to add a comment to the issue #538.
[14:15:09] [semantic-release] [@semantic-release/github] › ✖  Failed to add a comment to the issue #539.
[14:15:12] [semantic-release] [@semantic-release/github] › ✖  Failed to add a comment to the issue #541.
  semantic-release:github found semantic-release issues: [] +42s
[14:15:12] [semantic-release] › ✖  Failed step "success" of plugin "@semantic-release/github"
[14:15:12] [semantic-release] › ✖  An error occurred while running semantic-release: { HttpError: Invalid request.

For 'links/2/schema', {"labels"=>["released"]} is not an array.
    at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
  name: 'HttpError',
  status: 422,
  headers: 
   { 'access-control-allow-origin': '*',
     'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
     connection: 'close',
     'content-length': '209',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Fri, 14 Dec 2018 14:15:06 GMT',
     server: 'GitHub.com',
     status: '422 Unprocessable Entity',
     'strict-transport-security': 'max-age=31536000; includeSubdomains',
     'x-accepted-oauth-scopes': '',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-enterprise-version': '2.12.22',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'b067d086-6b6f-4824-92d1-c0791379a377',
     'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
     'x-runtime-rack': '0.023969',
     'x-xss-protection': '1; mode=block' },
  request: 
   { method: 'POST',
     url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/538/labels',
     headers: 
      { accept: 'application/vnd.github.v3+json',
        'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
        authorization: 'token [secure]',
        'content-type': 'application/json; charset=utf-8' },
     body: '{"labels":["released"]}',
     request: { validate: [Object] } },
  documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
  attemptNumber: 4,
  retriesLeft: 0,
  pluginName: '@semantic-release/github' }
[14:15:12] [semantic-release] › ✖  An error occurred while running semantic-release: { HttpError: Invalid request.

For 'links/2/schema', {"labels"=>["released"]} is not an array.
    at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
  name: 'HttpError',
  status: 422,
  headers: 
   { 'access-control-allow-origin': '*',
     'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
     connection: 'close',
     'content-length': '209',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Fri, 14 Dec 2018 14:15:09 GMT',
     server: 'GitHub.com',
     status: '422 Unprocessable Entity',
     'strict-transport-security': 'max-age=31536000; includeSubdomains',
     'x-accepted-oauth-scopes': '',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-enterprise-version': '2.12.22',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'c63d49e8-b108-43ce-9a88-b616e1fa3281',
     'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
     'x-runtime-rack': '0.029809',
     'x-xss-protection': '1; mode=block' },
  request: 
   { method: 'POST',
     url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/539/labels',
     headers: 
      { accept: 'application/vnd.github.v3+json',
        'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
        authorization: 'token [secure]',
        'content-type': 'application/json; charset=utf-8' },
     body: '{"labels":["released"]}',
     request: { validate: [Object] } },
  documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
  attemptNumber: 4,
  retriesLeft: 0,
  pluginName: '@semantic-release/github' }
[14:15:12] [semantic-release] › ✖  An error occurred while running semantic-release: { HttpError: Invalid request.

For 'links/2/schema', {"labels"=>["released"]} is not an array.
    at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
  name: 'HttpError',
  status: 422,
  headers: 
   { 'access-control-allow-origin': '*',
     'access-control-expose-headers': 'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
     connection: 'close',
     'content-length': '209',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Fri, 14 Dec 2018 14:15:12 GMT',
     server: 'GitHub.com',
     status: '422 Unprocessable Entity',
     'strict-transport-security': 'max-age=31536000; includeSubdomains',
     'x-accepted-oauth-scopes': '',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-enterprise-version': '2.12.22',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'bfcc035e-b3a3-4bbb-8ea7-c5207ade3b3d',
     'x-oauth-scopes': 'admin:public_key, public_repo, repo:status',
     'x-runtime-rack': '0.024596',
     'x-xss-protection': '1; mode=block' },
  request: 
   { method: 'POST',
     url: 'https://github.enterprise.com/api/v3/repos/ORG/plugin-cli/issues/541/labels',
     headers: 
      { accept: 'application/vnd.github.v3+json',
        'user-agent': 'octokit.js/16.2.0 Node.js/8.14.0 (Linux 3.13; x64)',
        authorization: 'token [secure]',
        'content-type': 'application/json; charset=utf-8' },
     body: '{"labels":["released"]}',
     request: { validate: [Object] } },
  documentation_url: 'https://developer.github.com/enterprise/2.12/v3/issues/labels/#add-labels-to-an-issue',
  attemptNumber: 4,
  retriesLeft: 0,
  pluginName: '@semantic-release/github' }
{ AggregateError: 
    HttpError: Invalid request.
    For 'links/2/schema', {"labels"=>["released"]} is not an array.
        at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
        at <anonymous>
    HttpError: Invalid request.
    For 'links/2/schema', {"labels"=>["released"]} is not an array.
        at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
        at <anonymous>
    HttpError: Invalid request.
    For 'links/2/schema', {"labels"=>["released"]} is not an array.
        at response.text.then.message (/home/circleci/project/node_modules/@octokit/request/lib/request.js:55:27)
        at <anonymous>
    at /home/circleci/project/node_modules/semantic-release/lib/plugins/pipeline.js:53:11
    at <anonymous> name: 'AggregateError' }error Command failed with exit code 1.
    at <anonymous> name: 'AggregateError' }error Command failed with exit code 1.

My config looks like:

➜ node release.config.js
config : {"prepare":["@semantic-release/npm","@semantic-release/git"],"plugins":["@semantic-release/commit-analyzer","@semantic-release/release-notes-generator","@semantic-release/npm",["@semantic-release/github",{"releasedLabels":false}]]}

Any help or direction on how to fix this would be wonderful. I'm not sure when it started, but it is making it hard to release continuously.

An in-range update of @octokit/rest is breaking the build 🚨

Version 15.5.0 of @octokit/rest was just published.

Branch	Build failing 🚨
Dependency	@octokit/rest
Current Version	15.4.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v15.5.0

15.5.0 (2018-05-14)

Bug Fixes

• routes: default header for checks APIs (96a2f95)
• amend accept header for github apps, keep custom accept headers intact (09e3c46)
• workaround for github.activity.markNotificationsAsRead() (#694) (c1fc675)

Features

• authentication type "app". "integration" is now deprecated (b56f0d2)

Commits

The new version differs by 14 commits.

• c1fc675 fix: workaround for github.activity.markNotificationsAsRead() (#694)
• 935c55c test: mark notifications as read
• be0be42 test: correctly authenticate as app
• 2f11117 refactor: remove obsolete application/vnd.github.machine-man-preview default header, it gets added automatically when authenticating as an app
• 09e3c46 fix: amend accept header for github apps, keep custom accept headers intact
• c614739 test: add machine preview header when authenticated as apps
• 96a2f95 fix(routes): default header for checks APIs
• 5c3d5a0 test: set default header for new checks API
• cde9ac2 test: custom headers are case insensitive
• 4eb46d8 test: case-insensitive accept header for #861
• b56f0d2 feat: authentication type "app". "integration" is now deprecated
• 2aa238b test: adapt app authentication test
• c2371ba deprecate: authentication type "integration"
• 726bf35 test: deprecate authentication type "integration"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 16.12.0 to 16.13.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v16.13.0

16.13.0 (2019-01-21)

Features

• "auth" constructor options (45a4836)

Commits

The new version differs by 10 commits.

• 0ae98ae refactor: github. -> octokit.
• 722fb21 docs(README): github. -> octokit.
• 6ee188a docs(HOW_IT_WORKS): replace .authenticate() method with auth construction option
• 3b81bea test: replace deprecated octokit.authenticate method with "auth" constructor option
• 162ab2b test: deprecated octokit.authenticate()
• 45a4836 feat: "auth" constructor options
• 1da3515 refactor: default constructor options to {} before passing to plugins
• 5c6bade test: "auth" constructor option
• 8b2ba2b docs(README): Replace depreceated octokit.authenticate with auth constructor option
• d7bced7 docs(README): update "API Previews"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

What are the minimum requirements for GH_TOKEN

When generating a GitHub token, what are the minimum scopes required?

I know the docs say "push access", but I am wondering specifically which boxes to check ha 😄

An in-range update of semantic-release is breaking the build 🚨

Version 15.8.1 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	15.8.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v15.8.1

15.8.1 (2018-07-18)

Bug Fixes

• do not override env variable with default if defined (3fb3fa8)

Commits

The new version differs by 1 commits.

• 3fb3fa8 fix: do not override env variable with default if defined

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of debug is breaking the build 🚨

Version 3.2.2 of debug was just published.

Branch	Build failing 🚨
Dependency	debug
Current Version	3.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 1 commits.

• 622e579 3.2.2

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Consistent HTTP 422 errors when publishing assets to GitHub release

👋

We're using semantic-release/github plugin to publish assets to each release we make with semantic-release.

The release configuration is as follows:

{
  "prepare": [
    "@semantic-release/npm",
    {
      "path": "@semantic-release/exec",
      "cmd": "npm i -g pkg && pkg ."
    }
  ],
  "publish": [
    "@semantic-release/npm",
    {
      "path": "@semantic-release/github",
      "assets": [
        {
          "path": "./snyk-linux",
          "name": "snyk-linux",
          "label": "snyk-linux"
        },
        {
          "path": "./snyk-macos",
          "name": "snyk-macos",
          "label": "snyk-macos"
        },
        {
          "path": "./snyk-win.exe",
          "name": "snyk-win.exe",
          "label": "snyk-win.exe"
        }
      ]
    }
  ]
}

The assets are being published as expected, however the plugin fails over a 422 response from GH:

[06:49:06] [semantic-release] › ✖  An error occurred while running semantic-release: { HttpError: {"message":"Validation Failed","request_id":"AA68:095A:1D9FF3:201218:5B7D0761","documentation_url":"https://developer.github.com/v3","errors":[{"resource":"ReleaseAsset","code":"already_exists","field":"name"}]}
    at response.text.then.message (/home/travis/.nvm/versions/node/v8.11.4/lib/node_modules/semantic-release/node_modules/@octokit/rest/lib/request/request.js:72:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  name: 'HttpError',
  code: 422,
  status: undefined,
  headers: 
   { 'cache-control': 'no-cache',
     connection: 'close',
     'content-length': '211',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Wed, 22 Aug 2018 06:49:06 GMT',
     'strict-transport-security': 'max-age=31557600',
     'x-accepted-oauth-scopes': 'repo',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'AA68:095A:1D9FF3:201218:5B7D0761',
     'x-oauth-scopes': 'repo',
     'x-xss-protection': '1; mode=block' },
  pluginName: '@semantic-release/github' }
{ HttpError: {"message":"Validation Failed","request_id":"AA68:095A:1D9FF3:201218:5B7D0761","documentation_url":"https://developer.github.com/v3","errors":[{"resource":"ReleaseAsset","code":"already_exists","field":"name"}]}
    at response.text.then.message (/home/travis/.nvm/versions/node/v8.11.4/lib/node_modules/semantic-release/node_modules/@octokit/rest/lib/request/request.js:72:19)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  name: 'HttpError',
  code: 422,
  status: undefined,
  headers: 
   { 'cache-control': 'no-cache',
     connection: 'close',
     'content-length': '211',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Wed, 22 Aug 2018 06:49:06 GMT',
     'strict-transport-security': 'max-age=31557600',
     'x-accepted-oauth-scopes': 'repo',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'AA68:095A:1D9FF3:201218:5B7D0761',
     'x-oauth-scopes': 'repo',
     'x-xss-protection': '1; mode=block' },
  pluginName: '@semantic-release/github' }

More details at https://travis-ci.org/snyk/snyk/jobs/419030290

I appreciate the fact this may be on GH side, opened a support ticket with them, will update here once I hear back.

Wanted to document the issue here, maybe there's more context?

Octokit proxy configuration

I have an enterprise github setup which is behind a proxy. Octokit supports this configuration but there is no notion to pass proxy configuration in @sementic-release/github library.

Am I missing something?

I have tested this by changing the Octokit initialization in the following line (It works!):
https://github.com/semantic-release/github/blob/master/lib/get-client.js#L105

Custom successComment not being used

I've only been using semantic-release for a few days, so I may not fully understand how it works, so this may just be my misunderstanding.

Here's a recent issue that was meant to use the below config: Colonise/DataSource#29

I've configured my package.json like so:

"publish": [
    {
        "path": "@semantic-release/github",
        "successComment": "This ${issue.pull_request ? 'pull request has been included in' : 'issue has been resolved in'} **[release ${nextRelease.gitTag}](https://github.com/Colonise/DataSource/releases/tag/${nextRelease.gitTag})**!\\n\\nYou can install the **[npm package](https://www.npmjs.com/package/@colonise/datasource)** for ${nextRelease.gitTag} using `npm install @colonise/datasource@${nextRelease.version}`\\n\\n_Automatically generated by [semantic-release](https://github.com/semantic-release/semantic-release)._",
        "failTitle": "The automatic publishing of release ${nextRelease.gitTag} is failing"
    },
    "@semantic-release/npm"
]

Permalink:
https://github.com/Colonise/DataSource/blob/dd0b873927dd54b451b8c1976d8034d98c35e586/package.json#L100-L104

Cheers

An in-range update of sinon is breaking the build 🚨

Version 4.1.6 of sinon was just published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	4.1.5
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 10 commits.

• 68c37ed Update docs/changelog.md and set new release id in docs/_config.yml
• cd8ae51 Add release documentation for v4.1.6
• 29e80be 4.1.6
• a5c59a5 Update History.md and AUTHORS for new release
• 0ae60b6 Merge pull request #1653 from mroderick/upgrade-dependencies
• dcd4191 Upgrade browserify to latest
• a316f02 Upgrade markdownlint-cli to latest
• 78ebdb3 Upgrade lint-staged to latest
• fcf967b Upgrade dependency supports-color
• 7c3cb4f Enable StaleBot with default configuration (#1649)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Getting an error during "success" plugin that I need help root-causing

I'm using semantic-release in a Drone CI + GitHub Enterprise setup. I have one project working successfully and have started updating our remaining JS projects to use semantic-release as well. I have run into a failure that I can't easily see what is happening:

This is the output:

[Semantic release]: Running semantic-release version 15.7.0
[Semantic release]: Load plugin "verifyConditions" from @semantic-release/npm
[Semantic release]: Load plugin "verifyConditions" from @semantic-release/github
[Semantic release]: Load plugin "analyzeCommits" from @semantic-release/commit-analyzer
[Semantic release]: Load plugin "generateNotes" from @semantic-release/release-notes-generator
[Semantic release]: Load plugin "prepare" from @semantic-release/npm
[Semantic release]: Load plugin "publish" from @semantic-release/npm
[Semantic release]: Load plugin "publish" from @semantic-release/github
[Semantic release]: Load plugin "success" from @semantic-release/github
[Semantic release]: Load plugin "fail" from @semantic-release/github
[Semantic release]: Run automated release from branch master
[Semantic release]: Call plugin "verifyConditions"
[Semantic release]: Verify authentication for registry https://registry.npmjs.itcs.hpecorp.net
[Semantic release]: Wrote NPM_TOKEN to .npmrc.
[Semantic release]: Call plugin "verifyConditions"
[Semantic release]: Verify GitHub authentication (https://github.hpe.com/api/v3)
[Semantic release]: Found git tag v1.0.1 associated with version 1.0.1
[Semantic release]: Found 1 commits since last release
[Semantic release]: Call plugin "analyzeCommits"
[Semantic release]: Analyzing commit: fix: replace broken link to wiki
[Semantic release]: The release type for the commit is patch
[Semantic release]: Analysis of 1 commits complete: patch release
[Semantic release]: The next release version is 1.0.2
[Semantic release]: Call plugin "generateNotes"
[Semantic release]: Call plugin "prepare"
[Semantic release]: Wrote version 1.0.2 to package.json
[Semantic release]: Wrote version 1.0.2 to package-lock.json
[Semantic release]: Create tag v1.0.2
[Semantic release]: Call plugin "publish"
[Semantic release]: Publishing version 1.0.2 to npm registry
+ @hpe/[email protected][Semantic release]: Call plugin "publish"
[Semantic release]: Published GitHub release: https://github.hpe.com/zookeeper/zookeeper/releases/tag/v1.0.2
[Semantic release]: Call plugin "success"
[Semantic release]: An error occurred while running semantic-release: { HttpError: {"message":"Validation Failed","errors":[{"message":"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.","resource":"Search","field":"q","code":"invalid"}],"documentation_url":"https://developer.github.com/enterprise/2.13/v3/search/"}
    at response.text.then.message (/drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/@octokit/rest/lib/request/request.js:78:19)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  name: 'HttpError',
  code: 422,
  status: undefined,
  headers:
   { 'access-control-allow-origin': '*',
     'access-control-expose-headers':
      'ETag, Link, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval',
     'cache-control': 'no-cache',
     connection: 'close',
     'content-length': '322',
     'content-security-policy': 'default-src \'none\'',
     'content-type': 'application/json; charset=utf-8',
     date: 'Tue, 10 Jul 2018 21:25:03 GMT',
     server: 'GitHub.com',
     status: '422 Unprocessable Entity',
     'strict-transport-security': 'max-age=31536000; includeSubdomains',
     'x-accepted-oauth-scopes': '',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-enterprise-version': '2.13.5',
     'x-github-media-type': 'github.v3; format=json',
     'x-github-request-id': 'b811cf9b-3264-43f4-b396-b1b0d84dde6f',
     'x-oauth-scopes': 'repo',
     'x-runtime-rack': '0.058855',
     'x-xss-protection': '1; mode=block' },
  pluginName: '@semantic-release/github' }
{ AggregateError: 
    HttpError: {"message":"Validation Failed","errors":[{"message":"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.","resource":"Search","field":"q","code":"invalid"}],"documentation_url":"https://developer.github.com/enterprise/2.13/v3/search/"}
        at response.text.then.message (/drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/@octokit/rest/lib/request/request.js:78:19)
    at /drone/src/github.hpe.com/zookeeper/zookeeper/node_modules/semantic-release/lib/plugins/pipeline.js:53:11 name: 'AggregateError' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @hpe/[email protected] semantic-release: `semantic-release`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @hpe/[email protected] semantic-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-07-10T21_25_03_520Z-debug.log

This is my .drone.yml pipeline step where I run semantic-release:

  semantic-release:
    image: node
    commands:
      - npm run semantic-release
    secrets: [ npm_token, github_token ]

This is my .releaserc:

{
    "branch": "master",
    "githubUrl": "https://github.hpe.com",
    "githubApiPathPrefix": "/api/v3"
}

It is getting all the way through publishing to our internal npm registry as well as creating the release in GitHub. The failure seems to be occurring where it is doing some kind of search related to updating issues or PRs?

Is there any additional debugging I can turn on? Is this something that is possibly documented already that I haven't found?

Thank you in advance

is .npmignore not respected?

while npm pack shows expected list of files, when i do release the package contains all the files from the project including those mentioned in .npmignore

dependencies:

        "@semantic-release/changelog": "^3.0.0",
        "@semantic-release/commit-analyzer": "^6.0.0",
        "@semantic-release/git": "^7.0.1",
        "@semantic-release/github": "^5.0.1",
        "@semantic-release/release-notes-generator": "^7.0.0",
        "semantic-release": "^15.8.1"

my .releaserc.json:

{
    "branch": "master",
    "debug": true,
    "noCi": true,
    "npmPublish": false,
    "githubUrl": "...",
    "githubApiPathPrefix": "...",
    "repository": {
        "type": "git",
        "url": "..."
    },
    "verifyConditions": [
        "@semantic-release/changelog",
        "@semantic-release/github"
    ],
    "getLastRelease": "@semantic-release/git",
    "prepare": [
        {
            "path": "@semantic-release/git",
            "assets": [
                "package.json",
                "CHANGELOG.md"
            ],
            "message": "chore(release): releasing ${nextRelease.version}\n\n${nextRelease.notes}"
        }
    ],
    "publish": [
        {
            "path": "@semantic-release/github",
            "assets": [
                "package.json",
                "CHANGELOG.md"
            ]
        }
    ]
}

if .npmignore is not the right file to filter out things that are added to the package, how else can i do that? i also tried files: [ ... ] in package.json - also does not help

Support globs for assets

https://github.com/cheton/github-release-cli and the Travis GitHub deploy provider support this.
One use case is it's nice to suffix the binary with the version string.

Recursively go through PRs when adding "included in release" message.

when working with feature branches, only the branch/PR itself gets a comment - it would be awesome if all PRs merged previously into feature branch also could get a comment. 🎉

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 15.15.1 to 15.16.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v15.16.0

15.16.0 (2018-11-05)

Bug Fixes

• routes: add +json format to preview accept headers (4302523)

Features

• .repos.updateInformationAboutPagesSite() (47d31e9)
• client.teams.addMember, client.teams.addOrUpdateProject, client.teams.createDiscussionComment, client.teams.createDiscussion, client.teams.deleteDiscussionComment, client.teams.deleteDiscussion, client.teams.getDiscussionComment, client.teams.getDiscussion, client.teams.getMember, client.teams.listDiscussionComments, client.teams.listDiscussions, client.teams.listProjects, client.teams.removeMember, client.teams.removeProject, client.teams.reviewProject, client.teams.updateDiscussionComment, client.teams.updateDiscussion (3ec71cb)

Commits

The new version differs by 5 commits.

• 3ec71cb feat: client.teams.addMember, client.teams.addOrUpdateProject, client.teams.createDiscussionComment, client.teams.createDiscussion, client.teams.deleteDiscussionComment, client.teams.deleteDiscussion, client.teams.getDiscussionComment, client.teams.getDiscussion, client.teams.getMember, client.teams.listDiscussionComments, client.teams.listDiscussions, client.teams.listProjects, client.teams.removeMember, client.teams.removeProject, client.teams.reviewProject, client.teams.updateDiscussionComment, client.teams.updateDiscussion
• 47d31e9 feat: .repos.updateInformationAboutPagesSite()
• 6c9d410 deprecate: add deprecation flag to aliases output.annotations[].filename, output.annotations[].warning_level, id alias for {project,column,card}_id, contentLength, contentType
• 4302523 fix(routes): add +json format to preview accept headers
• 33aba5d refactor: remove obsolete file

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of debug is breaking the build 🚨

Version 4.0.1 of debug was just published.

Branch	Build failing 🚨
Dependency	debug
Current Version	4.0.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes

4.0.1

This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.

Patches

• fix browserify and supply alternative unpkg entry point (closes #606): 99c95e3

Commits

The new version differs by 2 commits.

• 4490cd9 4.0.1
• 99c95e3 fix browserify and supply alternative unpkg entry point (closes #606)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Add label to PRs and issues fixed in a release

The label name should configurable. Ideally, once semantic-release/semantic-release#563 is implemented, it should contain a channel variable that will allow to generate a different label for channel on which the fix/feature is included.

For example with the label name released-in-${channel} we would add released-in-@next when releasing on @next and released-in-@latest once the release is added to @latest.

Search errors out with: The search is longer than 256

See https://travis-ci.org/semantic-release/semantic-release/jobs/340348136#L525

Verify condition fails on v5.2.4 with "HttpError: response.headers.entries(...) is not a function or its return value is not iterable"

Hey, we updated to v5.2.4 and verifyCondition started to fail as shown in our CircleCI build. We've reverted back to v5.2.1 and everything is working again. From looking at the release notes I can't see that this was intended, any idea what the issue could be?

An in-range update of semantic-release is breaking the build 🚨

Version 15.4.1 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	15.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v15.4.1

15.4.1 (2018-05-09)

Bug Fixes

• use git rev-parse origin/${branch} to verify origin head (d7081fa)

Commits

The new version differs by 1 commits.

• d7081fa fix: use git rev-parse origin/${branch} to verify origin head

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @octokit/rest is breaking the build 🚨

Version 15.4.1 of @octokit/rest was just published.

Branch	Build failing 🚨
Dependency	@octokit/rest
Current Version	15.4.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v15.4.1

15.4.1 (2018-05-11)

Bug Fixes

• validate: default to empty member array if optional parent parameter is not set (72bd9af)
• validate: default to empty member array if optional parent parameter is not set (2a69a3a)

Commits

The new version differs by 15 commits.

• 72bd9af fix(validate): default to empty member array if optional parent parameter is not set
• 2a69a3a fix(validate): default to empty member array if optional parent parameter is not set
• 8ad8919 build: routes
• b665a2b chore(package): update @octokit/routes to version 7.2.6
• d29eb23 chore(package): update @octokit/routes to version 7.2.5
• ef9dd1e ci(travis): fix syntax
• b716c30 build: routes
• 23510d8 chore(package): update @octokit/routes to version 7.2.4
• def5bca ci(travis): don’t fail if the greenkeeper script does not emit any changes
• 46d2396 ci(travis): don’t fail if the greenkeeper script does not emit any changes
• 4a227b4 ci(travis): set author when commiting changes in greenkeeper script
• a398df4 ci(travis): adapt greenkeeper script for routes updates
• 65c3a29 build: routes
• beef653 chore(package): update @octokit/routes to version 7.2.3
• 3aa8901 ci(travis): fix git push command for greenkeeper-routes-update

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @octokit/rest is breaking the build 🚨

Version 15.8.0 of @octokit/rest was just published.

Branch	Build failing 🚨
Dependency	@octokit/rest
Current Version	15.7.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v15.8.0

15.8.0 (2018-05-27)

Bug Fixes

• repository_id parameter is required for .search.labels() (b7e3add)
• don’t log same deprecation message twice (c745f7e)

Features

• actions{} parameter added to .checks.create() and .checks.update() (79925a1)
• response.headers (deprecates response.meta) (7ec8a03)
• response.status (5bf104c)

Commits

The new version differs by 20 commits.

• 347b59d refactor: response.meta -> response.headers
• 5bf104c feat: response.status
• 7ec8a03 feat: response.headers (deprecates response.meta)
• 244c7bf build: adapt typescript definitions for response.headers & response.data
• 8c38374 docs(README): show response status & headers in code examples
• 6b0f254 test: response.headers and response.status
• e386e7a test: adopt for deprecated parameter names
• 6584e60 build: routes for API docs
• c62b2bc deprecate: id parameter renamed to <resource>_id for several methods
• 59207cc deprecate: oldname parameter renamed to current_name for .issues.updateLabel()
• 79925a1 feat: actions{} parameter added to .checks.create() and .checks.update()
• b7e3add fix: repository_id parameter is required for .search.labels()
• a1b5242 refactor: deviate deprecation message from alias
• 82e6907 build(generate-routes): adapt from scope name change (migration -> migrations)
• 3283733 build(package): update @octokit/routes to version 8.0.1

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

How should rate limiting errors be handled?

I've run into a couple of situations where I'm bumping a few libraries quickly enough that I seem to hit the github API rate limit by the time semantic-release needs to do its thing. The current mode of failure is

• The build passes
• No npm release is published
• No github release is published
• I receive no indication whatsoever that a problem has been encountered

Once I'm in this state, someone usually comes up to me and tells me that no release was cut.

I think that a rate limit error should fail the build, so that when the github account comes out of the rate limit window, it can be manually restarted to attempt the same release again.

As it stands, I end up waiting for a half hour and making a trivial commit of some sort in order to trigger a new patch release.

github release / tag does not seem to include `package.json` with bumped version

e.g.

https://github.com/telusdigital/browserslist-config/blob/v1.0.0/package.json#L2

Next release version in assets path.

Are you interested in PR that adds ability to use variables in assets properties such as path and label?

Success comment lists release multiple times

Doing a first release resulted in the following success comment being added to two merged PRs:

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• v1.0.0
• GitHub release
• v1.0.0

Your semantic-release bot 📦🚀

Versions in use:

        "semantic-release": ">=16.0.0-beta <17.0.0",
        "@semantic-release/commit-analyzer": ">=7.0.0-beta <8.0.0",
        "@semantic-release/release-notes-generator": "^7.1.4",
        "@semantic-release/changelog": "^3.0.1",
        "@semantic-release/exec": ">=3.3.0-beta <4.0.0",
        "@semantic-release/git": ">=7.1.0-beta <8.0.0",
        "@semantic-release/npm": ">=5.2.0-beta <6.0.0",
        "@semantic-release/github": ">=5.3.0-beta <6.0.0"

Configuration used:

    "release": {
        "branches": [
            "+([1-9])?(.{+([1-9]),x}).x",
            "latest",
            "master",
            "next",
            "next-major",
            {"name": "prerelease", "prerelease": "prerelease"},
            {"name": "beta", "prerelease": "beta"},
            {"name": "alpha", "prerelease": "alpha"}
        ],
        "plugins": [
            ["@semantic-release/commit-analyzer", {
                "parserOpts": {
                    "revertPattern": "/^(?:Revert|revert:)\\s\"?([\\s\\S]+?)\"?\\s*This reverts commit (\\w*)\\./"
                },
                "releaseRules": "./release-rules.js"
            }],
            ["@semantic-release/release-notes-generator", {
                "parserOpts": {
                    "revertPattern": "/^(?:Revert|revert:)\\s\"?([\\s\\S]+?)\"?\\s*This reverts commit (\\w*)\\./"
                }
            }],
            ["@semantic-release/changelog", {
                "changelogFile": "./CHANGELOG.md"
            }],
            ["@semantic-release/npm", {
                "tarballDir": "./npm"
            }],
            ["@semantic-release/git", {
                "message": "chore(release): set version to ${nextRelease.version}\n\n${nextRelease.notes}",
                "assets": [
                    "../../../CHANGELOG.md",
                    "../../Package/package.json"
                ]
            }],
            ["@semantic-release/github", {
                "assets": [
                    {"path": "./npm", "label": "Package"}
                ]
            }],
            ["@semantic-release/exec", {
                "successCmd": "./some-script.sh"
            }]
        ]
    }

Note that I'm also using

    "private": true

in the package.json, so the npm plugin is actually not publishing - it's released on GitHub instead.

I tried finding the root of this but can't - I think it has to do with each plugin being able to return release information in the success step?

---

Thanks a lot for the hard work, semantic-release is an invaluable tool!

octokit.authenticate() is deprecated. Use "auth" constructor option instead

Hi,
I get following errors during running semantic-release version 15.13.3 in Travis CI. Who can help me to fix it. Thanks in advance.

[2:12:43 PM] [semantic-release] [@semantic-release/github] › ℹ  Verify GitHub authentication
Error: octokit.authenticate() is deprecated. Use "auth" constructor option instead.
    at authenticate (/home/travis/build/bndynet/bbootstrap/node_modules/@octokit/rest/plugins/authentication-deprecated/authenticate.js:4:16)
    at module.exports (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/lib/get-client.js:59:10)
    at module.exports (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/lib/verify.js:53:20)
    at verifyConditions (/home/travis/build/bndynet/bbootstrap/node_modules/@semantic-release/github/index.js:24:9)
    at validator (/home/travis/build/bndynet/bbootstrap/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
    at pReduce (/home/travis/build/bndynet/bbootstrap/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
    at Promise.all.then.value (/home/travis/build/bndynet/bbootstrap/node_modules/p-reduce/index.js:16:10)
    at process._tickCallback (internal/process/next_tick.js:68:7)

An in-range update of github is breaking the build 🚨

Version 12.0.7 of github was just published.

Branch	Build failing 🚨
Dependency	github
Current Version	12.0.6
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v12.0.7

12.0.7 (2017-11-28)

Bug Fixes

• whitelist X-GitHub-SSO header in response (#663) (1e07daf)

Commits

The new version differs by 3 commits.

• 1e07daf fix: whitelist X-GitHub-SSO header in response (#663)
• d5a3261 chore(package): @octokit/fixtures^5.4.0
• 081d5a0 test(scenario): search issues

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of prettier is breaking the build 🚨

Version 1.9.2 of prettier was just published.

Branch	Build failing 🚨
Dependency	prettier
Current Version	1.9.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of github is breaking the build 🚨

Version 12.0.4 of github was just published.

Branch	Build failing 🚨
Dependency	github
Current Version	12.0.3
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v12.0.4

12.0.4 (2017-11-22)

Bug Fixes

• package: update follow-redirects to version 1.2.6 (1667120)

Commits

The new version differs by 2 commits.

• 1667120 fix(package): update follow-redirects to version 1.2.6
• 309e66e docs(README): fixlink to promise example (#651)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Publish as pre-release?

Is there a way to publish as github pre-release? I couldn't find any setting unfortunately.

Thank you! L~

Release to different github repo?

Is there a way to release to a different github repository? What would be required to add that functionality?

Cheers, L~

Publish step returns 406, but tag was pushed to repo

I'm seeing an unexpected behavior during the publish step. I'm running a Jenkins job against Enterprise github. semantic-release is calculating the correct version based on the commit message and pushes a tag. GH responds with 406, the build fails, but the tag is successfully pushed to the repo.

What I understand 406 "Not Acceptable" to be is response given in place of a more cryptic one.
I can successfully generate and push a tag via the Jenkins job with git commands. Any ideas what the issue might be?

Config

"repository": {
  "type": "git",
  "url": "git@[enterprise.company.com]:[path]/[repo-name].git"
},
"keywords": ["fix", "feat", "chore"],
"release": {
  "analyzeCommits": "@semantic-release/commit-analyzer",
  "verifyConditions": "@semantic-release/npm",
  "generateNotes": "@semantic-release/release-notes-generator",
  "prepare": "@semantic-release/npm",
  "publish": "@semantic-release/github",
  "success": false,
  "fail": false,
  "branch": "origin/dev",
  "npmPublish": false
}

Job log

[14:24:31] [semantic-release] Created tag v0.15.1
[14:24:31] [semantic-release] Start step "publish" of plugin "@semantic-release/github"
[14:24:31] [semantic-release] [@semantic-release/github] Verify GitHub authentication (https://[enterprise.company.com])
[14:24:40] [semantic-release] » ×  Failed step "publish" of plugin "@semantic-release/github"

[14:24:40] [semantic-release]  An error occurred while running semantic-release: { HttpError
    at response.text.then.message (C:\Jenkins\jobs\semver-pipeline\workspace\node_modules\@octokit\request\lib\request.js:55:27)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  name: 'HttpError',
  status: 406,
  headers: 
   { 'cache-control': 'no-cache, no-store',
     connection: 'close',
     'content-security-policy': 'default-src \'none\'; base-uri \'self\'; block-all-mixed-content; connect-src \'self\' [enterprise.company.com] status.github.com wss://[enterprise.company.com]; font-src 
\'self\'; form-action \'self\' [enterprise.company.com]; frame-ancestors \'none\'; frame-src \'self\'; img-src * data:; manifest-src \'self\'; media-src \'none\'; script-src \'self\'; style-src 
\'unsafe-inline\' \'self\'',
     'content-type': 'text/html; charset=utf-8',
     date: 'Mon, 11 Feb 2019 19:24:41 GMT',
     'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
     server: 'GitHub.com',
     'set-cookie': 'has_recent_activity=1; path=/; expires=Mon, 11 Feb 2019 20:24:41 -0000, _fi_sess=MDEyOEZ5NXFTQ0tkK1dsZmMybk5Sa2FuL0RldldCY2RDbXZ3aVJYR0h3VzhmUDJxeUNDUVJTblFpNWRwcWNuMGtycXB
FcjV3Q1NVM1NwOFJTWldIRExnVTNTM2hNVG8xRDhUL1AyaitXUWZPNTdEeTJicEMyNE5vaXhUaFhtaklBQXFKNHE0RWN4OVdwbU01VEVJQzh3VjY1MGZDN01ubGpwMmlsbGJhNVM5QlRUK2pUaXNiamNtdCt5UzNTdVcyMmczOEFERE9XNCtHRmo5TzdSOWd
xeGVrTEVUOE5pcGpkTzZBcXhIc3FkQjlrbVE4OGVGeFhyaUpuQlYrMnFnK0hEVHk3dXI0YUx5eFVta0p5OXJNa3VuREhneXZsUUEzQlZiaVdjczNVNjQ4S1puQlMxSVAwalhQUzlMMDVPUkQtLXluNE1wQmh5eG9nY0hQbEVuQkQrcnc9PQ%3D%3D--c1b2e
f457aca21057a2f756d139bdf1db40dfd3d; path=/; secure; HttpOnly',
     status: '406 Not Acceptable',
     'strict-transport-security': 'max-age=31536000; includeSubdomains',
     'transfer-encoding': 'chunked',
     vary: 'X-PJAX',
     'x-content-type-options': 'nosniff',
     'x-frame-options': 'deny',
     'x-github-request-id': '6c023ef4-b4e1-4891-9ff2-7e0d4522e23d',
     'x-request-id': '1f966a6e-d362-4d1d-a253-80c5882a5a5d',
     'x-runtime': '0.008736',
     'x-runtime-rack': '0.013532',
     'x-xss-protection': '1; mode=block' },
  request: 
   { method: 'GET',
     url: 'https://[enterprise.company.com]/repos/[path]/[repo-name]',
     headers: 
      { accept: 'application/vnd.github.v3+json',
        'user-agent': 'octokit.js/16.13.3 Node.js/8.11.3 (Windows Server 2012; x64)',
        authorization: 'token [secure]' },
     request: { agent: undefined, validate: [Object] } },
  attemptNumber: 4,
  retriesLeft: 0,
  pluginName: '@semantic-release/github' }

Fails on "Invalid username or password" for git push permissions

Hi,

Seeing an error about semantic-release not able to push to github, even though the build has a GITHUB_TOKEN env var.

[semantic-release] › ✖  The command "git push --dry-run https://[secure]@www.github.com/lirantal/opn-shell.git HEAD:master" failed with the error message remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/lirantal/opn-shell.git/'

Travis build: https://travis-ci.org/lirantal/opn-shell/jobs/483803564

What should I be looking into?

An in-range update of github is breaking the build 🚨

Version 12.0.5 of github was just published.

Branch	Build failing 🚨
Dependency	github
Current Version	12.0.4
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

github is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v12.0.5

12.0.5 (2017-11-22)

Bug Fixes

• don’t pass filePath as query parameter (3c2e465)

Commits

The new version differs by 2 commits.

• 3c2e465 fix: don’t pass filePath as query parameter
• 11fed85 test(scenario): release assets

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Octokit dependency bump possibly should of been major

Octokit was upgraded from 15 to 16 in a patch version (https://github.com/semantic-release/github/releases/tag/v5.2.2), which has broken our GHE environment. According to this PR, it's an unintended side-effect (https://github.com/octokit/rest.js/issues/1127).

Not sure of the best approach here, but maybe major version bumps should coincide with a major release.

Beta: "Undefined" branch named in fail comment

I received the following header in the auto-created issue:

🚨 The automated release from the undefined branch failed. 🚨

---

It looks like fail.js isn't yet updated to the changes branches brought with it.

github/lib/fail.js

Line 12 in 9ab2cf2

options: {branch, repositoryUrl},

AFAICS (not a js guy myself 😅) options.branches would be the thing to use but that obviously doesn't work anymore for this logic of noting the branch the release failed on since it allows for multiple branches now. Perhaps the current branch/PR branch name needs to be used instead?

I can try to run this again with --debug if this information isn't enough, so please let me know.

Glob in `assets` field flattens paths... is this intentional?

This is more of a question than an issue, since maybe my configuration is wrong. My build creates files that have the same name; something like this:

dist/
    lib/
        merge.js
        merge.min.js
    browser/
        merge.js
        merge.min.js

In my release config, with github.assets configured as a glob:

assets: ['dist/{lib,umd,browser,module}/*.js']

or

assets: 'dist'

or

assets: ['dist/**/*']

my build in Travis CI would throw this Validation Failed / name exists error. Files were actually getting published to NPM and GitHub, but the GitHub release was flattening the paths, so only one of the merge.js and merge.min.js files was actually getting published to github.

When I configure each file individually in github.assets, like this:

assets: [{
    name: 'lib.merge.js'
    path: 'dist/lib/merge.js'
} ...]

the error goes away and all files are correctly released in github. I guess my questions are:

1. Is this intended behavior?
2. Is there a way to keep the folder structure for my github release?

It would be much easier to use a glob so I wouldn't have to explicitly set each file's name and path... and that would be the behavior I would expect from a glob. Any help on how to do this is much appreciated.

Include URL used when authenticating

I had this in the logs:

[Semantic release]: Call plugin verify-conditions
[Semantic release]: Verify authentication for registry https://artifacts.schibsted.io/artifactory/api/npm/npm-local/
[Semantic release]: Wrote NPM_USERNAME, NPM_PASSWORD and NPM_EMAIL to .npmrc.
[Semantic release]: An error occurred while running semantic-release: { [Error:  ]
  message: ' ',
  code: 406,
  status: 'Not Acceptable',
  headers: 

npm plugin write out the URL, but github did not. I figured out my issue (it was because my path prefix was the full path instead of just the path), but if the plugin had printed the url out before attempting the auth, that would have really helped.

(this was using semantic-release --debug, so I find it odd it did not print anything)

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 16.13.4 to 16.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v16.14.0

16.14.0 (2019-01-31)

Features

• custom logging (#1205) (cbb5c41)

Commits

The new version differs by 2 commits.

• cbb5c41 feat: custom logging (#1205)
• eac7427 docs(README): fix installation authentication example

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

adapt for latest @octokit/rest

In v15.2.0 we deprecated

• options.headers
• options.port
• options.pathPrefix
• options.host

in favour of options.baseUrl. That logs quite a lot of deprecation warnings in semantic-release now. I’ll fix that

An in-range update of bottleneck is breaking the build 🚨

Version 2.4.0 of bottleneck was just published.

Branch	Build failing 🚨
Dependency	bottleneck
Current Version	2.3.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

bottleneck is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 2 commits.

• ca30e1c 2.4.0
• b9d4a9b Reject duplicate IDs

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @octokit/rest is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 15.1.8 of @octokit/rest was just published.

Branch	Build failing 🚨
Dependency	@octokit/rest
Current Version	15.1.7
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v15.1.8

15.1.8 (2018-03-08)

Bug Fixes

• remove obsolete github.search.email() API (#795) (bf2f550)

Commits

The new version differs by 4 commits.

• bf2f550 fix: remove obsolete github.search.email() API (#795)
• 505ed1f chore(package): update semantic-release to version 15.0.0
• 60bdd7a docs(README): remove @next npm badge
• 44d6161 build(package): publish to @latest by default

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.12.0 to 15.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v15.12.1

15.12.1 (2018-11-21)

Bug Fixes

• push only tags to remote repo (2b082ac)

Commits

The new version differs by 10 commits.

• 2b082ac fix: push only tags to remote repo
• aa022e0 test: clarify variables name
• f2ede5b docs: typo in JS docs
• 9742712 test: verify errors have message and details
• 5937f13 test: fix typo
• 43dbd10 refactor: prefer filter shorter form
• 9f5645c refactor: harmonize git utils function names
• e594638 test: prefer array spread
• 244f014 docs: add Codefresh in list of CIs with pipelines
• 218d830 docs: fix quote marks (#986)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Success leaves comments on old PRs

The semantic-release module is an absolute lifesaver, and I have been using it for the hn module since its first release in august.

Last week, I merged another module (hn-react) into the main repository, making it a monorepo. It uses semantic-release-monorepo to make this work.

When yesterday I made the first release of hn-react from the monorepo, the release was successful. However, it left comments on all merged PRs. These PRs weren't related to the newly released commits, or even the hn-react module.

The release: https://travis-ci.org/headless-ninja/javascript/builds/364652080

Example comment: headless-ninja/javascript#1 (comment)

This doesn't look like expected behaviour.. is there some way to prevent this?

Related lines from the release

[Semantic release]: Running semantic-release version 15.1.5
[Semantic release]: Running semantic-release version 15.1.5
[Semantic release]: Found git tag hn-react-v1.7.11 associated with version 1.7.11
[Semantic release]: Call plugin analyze-commits
[Semantic release]: Found 7 commits for package hn-react since last release
[Semantic release]: Analysis of 7 commits complete: patch release
[Semantic release]: The next release version is 1.7.12
[Semantic release]: Call plugin verify-release
[Semantic release]: Call plugin generateNotes
[Semantic release]: Found 7 commits for package hn-react since last release
[Semantic release]: Call plugin prepare
[Semantic release]: Wrote version 1.7.12 to package.json
[Semantic release]: Create tag hn-react-v1.7.12
[Semantic release]: Call plugin publish
[Semantic release]: Publishing version 1.7.12 to npm registry
+ [email protected][Semantic release]: Published GitHub release: https://github.com/headless-ninja/javascript/releases/tag/hn-react-v1.7.12
[Semantic release]: Added comment to issue #24: https://github.com/headless-ninja/javascript/pull/24#issuecomment-380132006
[Semantic release]: Added comment to issue #17: https://github.com/headless-ninja/javascript/pull/17#issuecomment-380132016
[Semantic release]: Added comment to issue #16: https://github.com/headless-ninja/javascript/pull/16#issuecomment-380132024
[Semantic release]: Added comment to issue #15: https://github.com/headless-ninja/javascript/pull/15#issuecomment-380132034
[Semantic release]: Added comment to issue #14: https://github.com/headless-ninja/javascript/pull/14#issuecomment-380132042
[Semantic release]: Added comment to issue #13: https://github.com/headless-ninja/javascript/pull/13#issuecomment-380132052
[Semantic release]: Added comment to issue #3: https://github.com/headless-ninja/javascript/pull/3#issuecomment-380132062
[Semantic release]: Added comment to issue #1: https://github.com/headless-ninja/javascript/pull/1#issuecomment-380132068
[Semantic release]: Added comment to issue #23: https://github.com/headless-ninja/javascript/issues/23#issuecomment-380132077
[Semantic release]: Added comment to issue #2: https://github.com/headless-ninja/javascript/pull/2#issuecomment-380132085
[Semantic release]: Published release: 1.7.12

Fail to add comment to issues on other repo

See https://travis-ci.org/semantic-release/github/jobs/345779998#L506

We should probably exclude issues from other repo anyway, as we don't want to be invasive and add comments to someone else repo.

success plugin: Document criteria for PR match

After the success plugin was added, semantic-release posts (or attempts to) a comment to every single PR in the entire repository. I assumed this isn't the intended behavior, but it's not clear to me why this is happening? What are the criteria used to identify eligible PRs?

An in-range update of @octokit/rest is breaking the build 🚨

The dependency @octokit/rest was updated from 15.13.0 to 15.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v15.13.1

15.13.1 (2018-10-10)

Bug Fixes

• remove obsolete mapTo: input for .users.addEmails() (a44d541)
• remove obsolete preview headers (7b2c25a)

Commits

The new version differs by 6 commits.

• a44d541 fix: remove obsolete mapTo: input for .users.addEmails()
• 7b2c25a fix: remove obsolete preview headers
• afd7fdf test: replace test using obsolete preview header
• 89ab485 docs: remove obsolete client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()
• eb2c908 deprecate: client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()
• 88001fd test: deprecate client.gitdata.getCommitSignatureVerification() and client.gitdata.getTagSignatureVerification()

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of fs-extra is breaking the build 🚨

The dependency fs-extra was updated from 7.0.0 to 7.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

fs-extra is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 7 commits.

• a32c852 7.0.1
• 6392917 Temporarily disable standard-markdown
• ddc1a2f Fix removeSync() to eliminate spurious ENOTEMPTY errors on Windows (#646)
• ab254b1 Added docs/ and CHANGELOG.md to .npmignore (#642) (#643)
• 287f234 Fix typo in docs (#628)
• 402c1d0 Show support for mode (#587)
• 4da17fe Chore: github issue template (#617)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴