fix: clarify message for EGITNOPERMISSION error

docs: limit list of suggested tools for commit linting
fix(package): update read-pkg-up to version 7.0.0
2019-10-09 17:57:18 -04:00 · 2019-10-09 16:42:52 -04:00 · 2019-09-27 10:37:25 -07:00 · 2019-09-26 10:18:12 -07:00 · 2019-09-24 13:37:46 -07:00 · 2019-09-05 15:01:13 -07:00
50 changed files with 490 additions and 432 deletions
@@ -4,8 +4,9 @@ services:
  - docker

 node_js:
+  - 12
  - 10
-  - 8
+  - 8.3

 # Trigger a push build on master and greenkeeper branches + PRs build on every branches
 # Avoid double build on PRs (See https://github.com/travis-ci/travis-ci/issues/1147)
@@ -1,8 +1,8 @@
 <h1 align="center" style="border-bottom: none;">📦🚀 semantic-release</h1>
 <h3 align="center">Fully automated version management and package publishing</h3>
 <p align="center">
-  <a href="https://gitter.im/semantic-release/semantic-release">
-    <img alt="Gitter" src="https://badges.gitter.im/semantic-release/semantic-release.svg">
+  <a href="https://spectrum.chat/semantic-release">
+    <img alt="Join the community on Spectrum" src="https://withspectrum.github.io/badge/badge.svg">
  </a>
  <a href="https://travis-ci.org/semantic-release/semantic-release">
    <img alt="Travis" src="https://img.shields.io/travis/semantic-release/semantic-release/master.svg">
@@ -17,11 +17,6 @@
    <img alt="semantic-release" src="https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg">
  </a>
 </p>
-<p align="center">
-  <a href="https://waffle.io/semantic-release/semantic-release">
-    <img alt="Waffle.io" src="https://badge.waffle.io/semantic-release/semantic-release.svg?columns=all">
-  </a>
-</p>
 <p align="center">
  <a href="https://www.npmjs.com/package/semantic-release">
    <img alt="npm latest version" src="https://img.shields.io/npm/v/semantic-release/latest.svg">
@@ -57,7 +52,7 @@ This removes the immediate connection between human emotions and version numbers

 By default **semantic-release** uses [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines). The commit message format can be changed with the [`preset` or `config` options](docs/usage/configuration.md#options) of the [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer#options) and [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator#options) plugins.

-Tools such as [commitizen](https://github.com/commitizen/cz-cli), [commitlint](https://github.com/marionebl/commitlint) or [semantic-git-commit-cli](https://github.com/JPeer264/node-semantic-git-commit-cli) can be used to help contributors and enforce valid commit messages.
+Tools such as [commitizen](https://github.com/commitizen/cz-cli) or [commitlint](https://github.com/conventional-changelog/commitlint) can be used to help contributors and enforce valid commit messages.

 Here is an example of the release type that will be done based on a commit messages:

@@ -108,12 +103,13 @@ After running the tests, the command `semantic-release` will execute the followi
  - [Plugins](docs/extending/plugins-list.md)
  - [Shareable configuration](docs/extending/shareable-configurations-list.md)
 - Recipes
-  - [CI configurations](docs/recipes/README.md)
-  - [Package managers and languages](docs/recipes/README.md)
+  - [CI configurations](docs/recipes/README.md#ci-configurations)
+  - [Git hosted services](docs/recipes/README.md#git-hosted-services)
+  - [Package managers and languages](docs/recipes/README.md#package-managers-and-languages)
 - Developer guide
  - [JavaScript API](docs/developer-guide/js-api.md)
-  - [Plugins](docs/developer-guide/plugin.md)
-  - [Shareable configuration](docs/developer-guide/shareable-configuration.md)
+  - [Plugins development](docs/developer-guide/plugin.md)
+  - [Shareable configuration development](docs/developer-guide/shareable-configuration.md)
 - Support
  - [Resources](docs/support/resources.md)
  - [Frequently Asked Questions](docs/support/FAQ.md)
@@ -124,7 +120,7 @@ After running the tests, the command `semantic-release` will execute the followi
 ## Get help

 - [Stack Overflow](https://stackoverflow.com/questions/tagged/semantic-release)
- [Gitter chat](https://gitter.im/semantic-release/semantic-release)
+- [Spectrum community](https://spectrum.chat/semantic-release)
 - [Twitter](https://twitter.com/SemanticRelease)

 ## Badge
@@ -1,6 +1,7 @@
 # Summary

 ## Usage
+- [Getting started](docs/usage/getting-started.md#getting-started)
 - [Installation](docs/usage/installation.md#installation)
 - [CI Configuration](docs/usage/ci-configuration.md#ci-configuration)
 - [Configuration](docs/usage/configuration.md#configuration)
@@ -12,19 +13,18 @@
 - [Shareable configuration](docs/extending/shareable-configurations-list.md)

 ## Recipes
- [CI configurations](docs/recipes/README.md)
-	- [CircleCI 2.0 workflows](docs/recipes/circleci-workflows.md)
+- [CI configurations](docs/recipes/README.md#ci-configurations)
+	- [CircleCI 2.0](docs/recipes/circleci-workflows.md)
 	- [Travis CI](docs/recipes/travis.md)
-	- [Travis CI with build stages](docs/recipes/travis-build-stages.md)
 	- [GitLab CI](docs/recipes/gitlab-ci.md)
- [Git hosted services](docs/recipes/README.md)
+- [Git hosted services](docs/recipes/README.md#git-hosted-services)
 	- [Git authentication with SSH keys](docs/recipes/git-auth-ssh-keys.md)
- [Package managers and languages](docs/recipes/README.md)
+- [Package managers and languages](docs/recipes/README.md#package-managers-and-languages)

 ## Developer guide
 - [JavaScript API](docs/developer-guide/js-api.md)
- [Plugin](docs/developer-guide/plugin.md)
- [Shareable configuration](docs/developer-guide/shareable-configuration.md)
+- [Plugin development](docs/developer-guide/plugin.md)
+- [Shareable configuration development](docs/developer-guide/shareable-configuration.md)

 ## Support
 - [Resources](docs/support/resources.md)
@@ -3,7 +3,7 @@
 // Bad news: We have to write plain ES5 in this file
 // Good news: It's the only file of the entire project

-/* eslint-disable no-var, promise/prefer-await-to-then, prefer-destructuring */
+/* eslint-disable no-var */

 var semver = require('semver');
 var execa = require('execa');
@@ -21,9 +21,8 @@ See https://github.com/semantic-release/semantic-release/blob/master/docs/suppor
  process.exit(1);
 }

-execa
-  .stdout('git', ['--version'])
-  .then(stdout => {
+execa('git', ['--version'])
+  .then(({stdout}) => {
    var gitVersion = findVersions(stdout)[0];
    if (semver.lt(gitVersion, MIN_GIT_VERSION)) {
      console.error(`[semantic-release]: Git version ${MIN_GIT_VERSION} is required. Found ${gitVersion}.`);
@@ -1,4 +1,4 @@
-const {argv, env, stderr} = require('process');
+const {argv, env, stderr} = require('process'); // eslint-disable-line node/prefer-global/process
 const util = require('util');
 const hideSensitive = require('./lib/hide-sensitive');

@@ -47,21 +47,18 @@ Usage:
      return 0;
    }

-    // Set the `noCi` options as yargs sets the `ci` options instead (because arg starts with `--no`)
-    if (opts.ci === false) {
-      opts.noCi = true;
-    }
-
    if (opts.debug) {
      // Debug must be enabled before other requires in order to work
      require('debug').enable('semantic-release:*');
    }
+
    await require('.')(opts);
    return 0;
  } catch (error) {
    if (error.name !== 'YError') {
      stderr.write(hideSensitive(env)(util.inspect(error, {colors: true})));
    }
+
    return 1;
  }
 };
@@ -39,7 +39,7 @@ try {
    }

    for (const release of releases) {
-      console.log(`The release was published with plugin "${pluginName}".`);
+      console.log(`The release was published with plugin "${release.pluginName}".`);
    }
  } else {
    console.log('No release published.');
@@ -1 +1,106 @@
-# Plugin developer guide
+# Plugin Developer Guide
+
+To create a plugin for `semantic-release`, you need to decide which parts of the release lifecycle are important to that plugin. For example, it is best to always have a `verify` step because you may be receiving inputs from a user and want to make sure they exist. A plugin can abide by any of the following lifecycles:
+
+- `verify`
+- `prepare`
+- `publish`
+- `success`
+- `fail`
+
+`semantic-release` will require the plugin via `node` and look through the required object for methods named like the lifecyles stated above. For example, if your plugin only had a `verify` and `success` step, the `main` file for your object would need to `export` an object with `verify` and `success` functions.
+
+In addition to the lifecycle methods, each lifecyle is passed two objects:
+
+1. `pluginConfig` - an object containing the options that a user may pass in via their `release.config.js` file (or similar)
+2. `context` - provided by `semantic-release` for access to things like `env` variables set on the running process.
+
+For each lifecycle you create, you will want to ensure it can accept `pluginConfig` and `context` as parameters.
+
+## Creating a Plugin Project
+
+It is recommended that you generate a new project with `yarn init`. This will provide you with a basic node project to get started with. From there, create an `index.js` file, and make sure it is specified as the `main` in the `package.json`. We will use this file to orchestrate the lifecycle methods later on.
+
+Next, create a `src` or `lib` folder in the root of the project. This is where we will store our logic and code for how our lifecycle methods work. Finally, create a `test` folder so you can write tests related to your logic.
+
+We recommend you setup a linting system to ensure good javascript practices are enforced. ESLint is usually the system of choice, and the configuration can be whatever you or your team fancies.
+
+## Exposing Lifecycle Methods
+
+In your `index.js` file, you can start by writing the following code
+
+```javascript
+const verifyConditions = require('./src/verify');
+
+let verified;
+
+/**
+ * Called by semantic-release during the verification step
+ * @param {*} pluginConfig The semantic-release plugin config
+ * @param {*} context The context provided by semantic-release
+ */
+async function verify(pluginConfig, context) {
+  await verifyConditions(pluginConfig, context);
+  verified = true;
+}
+
+module.exports = { verify };
+```
+
+Then, in your `src` folder, create a file called `verify.js` and add the following
+
+```javascript
+const AggregateError = require('aggregate-error');
+
+/**
+ * A method to verify that the user has given us a slack webhook url to post to
+ */
+module.exports = async (pluginConfig, context) => {
+  const { logger } = context;
+  const errors = [];
+
+  // Throw any errors we accumulated during the validation
+  if (errors.length > 0) {
+    throw new AggregateError(errors);
+  }
+};
+```
+
+As of right now, this code won't do anything. However, if you were to run this plugin via `semantic-release`, it would run when the `verify` step occurred.
+
+Following this structure, you can create different steps and checks to run through out the release process.
+
+## Supporting Options
+
+Let's say we want to verify that an `option` is passed. An `option` is a configuration object that is specific to your plugin. For example, the user may set an `option` in their release config like:
+
+```js
+{
+    prepare: {
+        path: "@semantic-release/my-special-plugin"
+        message: "My cool release message"
+    }
+}
+```
+
+This `message` option will be passed to the `pluginConfig` object mentioned earlier. We can use the validation method we created to verify this option exists so we can perform logic based on that knowledge. In our `verify` file, we can add the following:
+
+```js
+const { message } = pluginConfig;
+
+if (message.length) {
+    //...
+}
+```
+
+## Supporting Environment Variables
+
+Similar to `options`, environment variables exist to allow users to pass tokens and set special URLs. These are set on the `context` object instead of the `pluginConfig` object. Let's say we wanted to check for `GITHUB_TOKEN` in the environment because we want to post to GitHub on the user's behalf. To do this, we can add the following to our `verify` command:
+
+```js
+const { env } = context;
+
+if (env.GITHUB_TOKEN) {
+    //...
+}
+```
@@ -2,15 +2,19 @@

 ## Official plugins
 - [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer)
+  - **Note**: this is already part of semantic-release and does not have to be installed separately
  - `analyzeCommits`: Determine the type of release by analyzing commits with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
 - [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator)
+  - **Note**: this is already part of semantic-release and does not have to be installed separately
  - `generateNotes`: Generate release notes for the commits added since the last release with [conventional-changelog](https://github.com/conventional-changelog/conventional-changelog)
 - [@semantic-release/github](https://github.com/semantic-release/github)
+  - **Note**: this is already part of semantic-release and does not have to be installed separately
  - `verifyConditions`: Verify the presence and the validity of the GitHub authentication and release configuration
  - `publish`: Publish a [GitHub release](https://help.github.com/articles/about-releases)
  - `success`: Add a comment to GitHub issues and pull requests resolved in the release
  - `fail`: Open a GitHub issue when a release fails
 - [@semantic-release/npm](https://github.com/semantic-release/npm)
+  - **Note**: this is already part of semantic-release and does not have to be installed separately
  - `verifyConditions`: Verify the presence and the validity of the npm authentication and release configuration
  - `prepare`: Update the package.json version and create the npm package tarball
  - `publish`: Publish the package on the npm registry
@@ -26,23 +30,31 @@
 - [@semantic-release/exec](https://github.com/semantic-release/exec)
  - `verifyConditions`: Execute a shell command to verify if the release should happen
  - `analyzeCommits`: Execute a shell command to determine the type of release
-  - `verifyRelease`: Execute a shell command to verifying a release that was determined before and is about to be published.
+  - `verifyRelease`: Execute a shell command to verifying a release that was determined before and is about to be published
  - `generateNotes`: Execute a shell command to generate the release note
  - `prepare`: Execute a shell command to prepare the release
  - `publish`: Execute a shell command to publish the release
  - `success`: Execute a shell command to notify of a new release
  - `fail`: Execute a shell command to notify of a failed release
+- [@semantic-release/apm](https://github.com/semantic-release/apm)
+  - `verifyConditions`: Verify the presence of the `ATOM_ACCESS_TOKEN` environment variable and the [`apm`](https://github.com/atom/apm) CLI
+  - `prepare`: Update the `package.json` version with [`npm version`](https://docs.npmjs.com/cli/version)
+  - `publish`: Publish the [Atom package](https://flight-manual.atom.io/hacking-atom/sections/publishing)

 ## Community plugins

 [Open a Pull Request](https://github.com/semantic-release/semantic-release/blob/master/CONTRIBUTING.md#submitting-a-pull-request) to add your plugin to the list.

+- [semantic-release-slack-bot](https://github.com/juliuscc/semantic-release-slack-bot)
+  - `verifyConditions`: Verify that the environment variable `SLACK_WEBHOOK` has been defined.
+  - `success`: Publish a message about the success to a slack channel.
+  - `fail`: Optionally publish a message about failure to a slack channel.
 - [semantic-release-docker](https://github.com/felixfbecker/semantic-release-docker)
  - `verifyConditions`: Verify that all needed configuration is present and login to the Docker registry.
-  - `publish`: Tag the image specified by `name` with the new version, push it to Docker Hub and update the latest tag.
+  - `publish`: Tag the image specified by `name` with the new version, push it to Docker Hub and update the latest tag
 - [semantic-release-gcr](https://github.com/carlos-cubas/semantic-release-gcr)
-  - `verifyConditions`: Verify that all needed configuration is present and login to the Docker registry.
-  - `publish`: Tag the image specified by `name` with the new version, push it to Docker Hub and update the latest tag.
+  - `verifyConditions`: Verify that all needed configuration is present and login to the Docker registry
+  - `publish`: Tag the image specified by `name` with the new version, push it to Docker Hub and update the latest tag
 - [semantic-release-vsce](https://github.com/raix/semantic-release-vsce)
  - `verifyConditions`: Verify the presence and the validity of the vsce authentication and release configuration
  - `prepare`: Create a `.vsix` for distribution
@@ -51,14 +63,31 @@
  - `verifyConditions`: Check the dependencies format against a regexp before a release
 - [semantic-release-chrome](https://github.com/GabrielDuarteM/semantic-release-chrome)
  - `verifyConditions`: Verify the presence of the authentication (set via environment variables)
-  - `prepare`: Write the correct version to the manifest.json and creates a zip file of the whole dist folder
+  - `prepare`: Write the correct version to the `manifest.json` and creates a zip file of the whole dist folder
  - `publish`: Uploads the generated zip file to the webstore, and publish the item
 - [semantic-release-firefox](https://github.com/felixfbecker/semantic-release-firefox)
  - `verifyConditions`: Verify the presence of the authentication (set via environment variables)
-  - `prepare`: Write the correct version to the manifest.json,   creates a xpi file of the dist folder and a zip of the sources
+  - `prepare`: Write the correct version to the `manifest.json`, creates a `xpi` file of the dist folder and a zip of the sources
  - `publish`: Submit the generated archives to the webstore for review, and publish the item including release notes
 - [semantic-release-gerrit](https://github.com/pascalMN/semantic-release-gerrit)
  - `generateNotes`: Generate release notes with Gerrit reviews URL
 - [semantic-release-expo](https://github.com/bycedric/semantic-release-expo)
  - `verifyConditions`: Verify Expo manifest(s) are readable and valid.
  - `prepare`: Update version, ios build number and android version code in the Expo manifest(s).
+- [maven-semantic-release](https://github.com/conveyal/maven-semantic-release)
+  - `verifyConditions`: Verifies that the `pom.xml` file and other files exist and are setup to allow releases
+  - `verifyRelease`: Checks and warns (does not error by default) if the version numbers found on maven central and within the Git project differ by quite a bit
+  - `prepare`: Changes the version number in the `pom.xml` (or all `pom.xml` files in maven projects with multiple `pom.xml` files) and optionally creates a commit with this version number and pushes it to `master`
+  - `publish`: Runs `mvn deploy` to deploy to maven central and optionally will update to next snapshot version and merge changes to development branch
+- [semantic-release-ado](https://github.com/lluchmk/semantic-release-ado)
+  - `prepare`: Stores the version number as an Azure DevOps pipeline variable availabe to downstream steps on the job
+- [gradle-semantic-release](https://github.com/KengoTODA/gradle-semantic-release-plugin)
+  - `verifyConditions`: Verify that project has a Gradle wrapper script, and `build.gradle` contains a task to publish artifacts.
+  - `prepare`: Changes the version number in the `gradle.properties`
+  - `publish`: Triggers Gradle to publish artifacts.
+- [semantic-release-circleci-orb](https://github.com/matt-oakes/semantic-release-circleci-orb)
+  - `verifyConditions`: Verify the presence of the `CIRCLECI_API_TOKEN` environment variable, `orbName` option, and the `circleci` CLI.
+  - `publish`: Publish the CircleCI orb.
+- [semantic-release-github-pages](https://github.com/qiwi/semantic-release-gh-pages-plugin)
+  - `verifyConditions`: Verify the presence of the auth token set via environment variables.
+  - `publish`: Pushes commit to the documentation branch.
@@ -5,3 +5,9 @@
 - [@semantic-release/gitlab-config](https://github.com/semantic-release/gitlab-config) - semantic-release shareable configuration for GitLab

 ## Community configurations
+- [@jedmao/semantic-release-npm-github-config](https://github.com/jedmao/semantic-release-npm-github-config)
+  - Provides an informative [git](https://github.com/semantic-release/git) commit message for the release commit that does not trigger continuous integration and conforms to the [conventional commits specification](https://www.conventionalcommits.org/) (e.g., "chore(release): 1.2.3 [skip ci]\n\nnotes").
+  - Creates a tarball that gets uploaded with each [GitHub release](https://github.com/semantic-release/github).
+  - Publishes the same tarball to [npm](https://github.com/semantic-release/npm).
+  - Commits the version change in `package.json`.
+  - Creates or updates a [changelog](https://github.com/semantic-release/changelog) file.
@@ -3,7 +3,6 @@
 ## CI configurations
 - [CircleCI 2.0 workflows](circleci-workflows.md)
 - [Travis CI](travis.md)
- [Travis CI with build stages](travis-build-stages.md)
 - [GitLab CI](gitlab-ci.md)

 ## Git hosted services
@@ -4,7 +4,7 @@

 The [Authentication](../usage/ci-configuration.md#authentication) environment variables can be configured in [CircleCi Project Settings](https://circleci.com/docs/2.0/env-vars/#adding-environment-variables-in-the-app)..

-Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../usage/ci-configuration.md#automatic-setup-with-semantic-release-cli).
+Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../usage/getting-started.md#getting-started).

 ## Multiple Node jobs configuration

@@ -137,7 +137,7 @@ jobs:
          # Make sure only the current user can read the private key
          - chmod 600 /tmp/git_deploy_key
          # Create a script to return the passphrase environment variable to ssh-add
-          - echo 'echo ${SSH_PASSPHRASE}' > /tmp/askpass && chmod +x /tmp/askpass
+          - echo 'echo ${SSL_PASSPHRASE}' > /tmp/askpass && chmod +x /tmp/askpass
          # Start the authentication agent
          - eval "$(ssh-agent -s)"
          # Add the key to the authentication agent
@@ -158,6 +158,6 @@ Commit the encrypted private key and the `.circleci/config.yml` file to your rep

 ```bash
 $ git add git_deploy_key.enc .circleci/config.yml
-$ git commit -m "ci(cicle): Add the encrypted private ssh key"
+$ git commit -m "ci(circle): Add the encrypted private ssh key"
 $ git push
 ```
@@ -1,95 +0,0 @@
-# Using semantic-release with [Travis CI build stages](https://docs.travis-ci.com/user/build-stages)
-
-## Environment variables
-
-The [Authentication](../usage/ci-configuration.md#authentication) environment variables can be configured in [Travis Repository Settings](https://docs.travis-ci.com/user/environment-variables/#defining-variables-in-repository-Settings) or with the [travis env set CLI](https://github.com/travis-ci/travis.rb#env).
-
-Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../usage/ci-configuration.md#automatic-setup-with-semantic-release-cli).
-
-## Multiple Node jobs configuration
-
-### `.travis.yml` configuration for multiple Node jobs
-
-This example is a minimal configuration for **semantic-release** with a build running Node 6 and 8. See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.
-
-This example creates a `release` [build stage](https://docs.travis-ci.com/user/build-stages) that [runs `semantic-release` only after all test jobs are successful](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).
-
-It's recommended to run the `semantic-release` command in the [Travis `deploy` step](https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle) so if an error occurs the build will fail and Travis will send a notification.
-
-**Note**: It's not recommended to run the `semantic-release` command in the Travis `script` step as each script in this step will be executed regardless of the outcome of the previous one. See [travis-ci/travis-ci#1066](https://github.com/travis-ci/travis-ci/issues/1066).
-
-**Advanced configuration**: Running the tests in the `script` step of the `release` stage is not necessary as the previous stage(s) already ran them. To increase speed, the `script` step of the `release` stage can be overwritten to skip the tests. Note that other commands such as build or compilation might still be required.
-
-```yaml
-language: node_js
-
-node_js:
-  - 8
-  - 6
-
-jobs:
-  include:
-    # Define the release stage that runs semantic-release
-    - stage: release
-      node_js: lts/*
-      # Advanced: optionally overwrite your default `script` step to skip the tests
-      # script: skip
-      deploy:
-        provider: script
-        skip_cleanup: true
-        script:
-          - npx semantic-release
-```
-
-### `package.json` configuration for multiple Node jobs
-
-A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
-
-```json
-{
-  "devDependencies": {
-    "semantic-release": "^15.0.0"
-  }
-}
-```
-
-## Non-JavaScript projects configuration
-
-For projects that require to be tested with one or multiple version of a Non-JavaScript [language](https://docs.travis-ci.com/user/languages), optionally on multiple [Operating Systems](https://docs.travis-ci.com/user/multi-os).
-
-This recipe cover the Travis specifics only. See [Non JavaScript projects recipe](../support/FAQ.md#can-i-use-semantic-release-to-publish-non-javascript-packages) for more information on the **semantic-release** configuration.
-
-### `.travis.yml` configuration for non-JavaScript projects
-
-This example is a minimal configuration for **semantic-release** with a build running [Go 1.6 and 1.7](https://docs.travis-ci.com/user/languages/go). See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.
-
-This example creates a `release` [build stage](https://docs.travis-ci.com/user/build-stages) that [runs `semantic-release` only after all test jobs are successful](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).
-
-It's recommended to run the `semantic-release` command in the [Travis `deploy` step](https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle) so if an error occurs the build will fail and Travis will send a notification.
-
-**Note**: It's not recommended to run the `semantic-release` command in the Travis `script` step as each script in this step will be executed regardless of the outcome of the previous one. See [travis-ci/travis-ci#1066](https://github.com/travis-ci/travis-ci/issues/1066).
-
-**Advanced configuration**: Running the tests in the `script` step of the `release` stage is not necessary as the previous stage(s) already ran them. To increase speed, the `script` step of the `release` stage can be overwritten to skip the tests. Note that other commands such as build or compilation might still be required.
-
-```yaml
-language: go
-
-go:
-  - 1.6
-  - 1.7
-
-jobs:
-  include:
-    # Define the release stage that runs semantic-release
-    - stage: release
-      # Advanced: optionally overwrite your default `script` step to skip the tests
-      # script:
-      #   - make
-      deploy:
-        provider: script
-        skip_cleanup: true
-        script:
-          # Use nvm to install and use the Node LTS version (nvm is installed on all Travis images)
-          - nvm install lts/*
-          - npx semantic-release
-```
@@ -4,62 +4,22 @@

 The [Authentication](../usage/ci-configuration.md#authentication) environment variables can be configured in [Travis Repository Settings](https://docs.travis-ci.com/user/environment-variables/#defining-variables-in-repository-Settings) or with the [travis env set CLI](https://github.com/travis-ci/travis.rb#env).

-Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../usage/ci-configuration.md#automatic-setup-with-semantic-release-cli).
+Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../usage/getting-started.md#getting-started).

-## Single Node job configuration
+## Node.js projects configuration

-For projects that require to be tested only with a single [Node version](https://docs.travis-ci.com/user/getting-started/#Selecting-a-different-programming-language) on [one Operating System](https://docs.travis-ci.com/user/getting-started/#Selecting-infrastructure-(optional)).
-
-**Note**: [Node 8 is the minimal version required](../support/FAQ.md#why-does-semantic-release-require-node-version--83).
-
-### `.travis.yml` configuration for single Node job
-
-This example is a minimal configuration for semantic-release with a build running Node 8 on Linux. See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.
-
-It's recommended to run the `semantic-release` command in the [Travis `deploy` step](https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle) so if an error occurs the build will fail and Travis will send a notification.
-
-**Note**: It's not recommended to run the `semantic-release` command in the Travis `script` step as each script in this step will be executed regardless of the outcome of the previous one. See [travis-ci/travis-ci#1066](https://github.com/travis-ci/travis-ci/issues/1066).
-
-```yaml
-language: node_js
-
-node_js: 8
-
-deploy:
-  provider: script
-  skip_cleanup: true
-  script:
-    - npx semantic-release
-```
-
-### `package.json` configuration for single Node job
-
-A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
-
-```json
-{
-  "devDependencies": {
-    "semantic-release": "^11.0.0"
-  }
-}
-```
-
-## Multiple Node jobs configuration
-
-For projects that require to be tested with multiple [Node versions](https://docs.travis-ci.com/user/languages/javascript-with-nodejs/#Specifying-Node.js-versions) and/or on multiple [Operating Systems](https://docs.travis-ci.com/user/multi-os).
-
-**Note**: At least one job must run a [Node >= 8 version](../support/FAQ.md#why-does-semantic-release-require-node-version--83).
-
-### `.travis.yml` configuration for multiple Node jobs
+### `.travis.yml` configuration for multiple Node.js jobs

 This example is a minimal configuration for **semantic-release** with a build running Node 6 and 8. See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.

-This example uses [`travis-deploy-once`](https://github.com/semantic-release/travis-deploy-once) in order to [Run `semantic-release` only after all tests succeeded](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded). Alternatively you can use [Travis CI Build Stages recipe](travis-build-stages.md).
+This example creates a `release` [build stage](https://docs.travis-ci.com/user/build-stages) that [runs `semantic-release` only after all test jobs are successful](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).

 It's recommended to run the `semantic-release` command in the [Travis `deploy` step](https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle) so if an error occurs the build will fail and Travis will send a notification.

 **Note**: It's not recommended to run the `semantic-release` command in the Travis `script` step as each script in this step will be executed regardless of the outcome of the previous one. See [travis-ci/travis-ci#1066](https://github.com/travis-ci/travis-ci/issues/1066).

+**Advanced configuration**: Running the tests in the `script` step of the `release` stage is not necessary as the previous stage(s) already ran them. To increase speed, the `script` step of the `release` stage can be overwritten to skip the tests. Note that other commands such as build or compilation might still be required.
+
 ```yaml
 language: node_js

@@ -67,15 +27,20 @@ node_js:
  - 8
  - 6

-deploy:
-  provider: script
-  skip_cleanup: true
-  script:
-    - npx travis-deploy-once "npx semantic-release"
+jobs:
+  include:
+    # Define the release stage that runs semantic-release
+    - stage: release
+      node_js: lts/*
+      # Advanced: optionally overwrite your default `script` step to skip the tests
+      # script: skip
+      deploy:
+        provider: script
+        skip_cleanup: true
+        script:
+          - npx semantic-release
 ```

-**Note**: See the `travis-deploy-once` [`pro`](https://github.com/semantic-release/travis-deploy-once#-p---pro) and [`travis-url`](https://github.com/semantic-release/travis-deploy-once#-u---travis-url) options for using with [Travis Pro](https://docs.travis-ci.com/user/travis-pro) and [Travis Enterprise](https://enterprise.travis-ci.com).
-
 ### `package.json` configuration for multiple Node jobs

 A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
@@ -83,13 +48,12 @@ A `package.json` is required only for [local](../usage/installation.md#local-ins
 ```json
 {
  "devDependencies": {
-    "semantic-release": "^15.0.0",
-    "travis-deploy-once": "^5.0.0"
+    "semantic-release": "^15.0.0"
  }
 }
 ```

-## Non-JavaScript projects configuration
+## Non-Node.js projects configuration

 For projects that require to be tested with one or multiple version of a Non-JavaScript [language](https://docs.travis-ci.com/user/languages), optionally on multiple [Operating Systems](https://docs.travis-ci.com/user/multi-os).

@@ -97,14 +61,16 @@ This recipe cover the Travis specifics only. See [Non JavaScript projects recipe

 ### `.travis.yml` configuration for non-JavaScript projects

-This example is a minimal configuration for **semantic-release** with a build running [Go 1.6 and 1.7](https://docs.travis-ci.com/user/languages/go) on Linux and OSX. See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.
+This example is a minimal configuration for **semantic-release** with a build running [Go 1.6 and 1.7](https://docs.travis-ci.com/user/languages/go). See [Travis - Customizing the Build](https://docs.travis-ci.com/user/customizing-the-build) for additional configuration options.

-This example uses [`travis-deploy-once`](https://github.com/semantic-release/travis-deploy-once) in order to [run `semantic-release` only after all tests succeeded](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded). Alternatively you can use [Travis CI Build Stages recipe](travis-build-stages.md).
+This example creates a `release` [build stage](https://docs.travis-ci.com/user/build-stages) that [runs `semantic-release` only after all test jobs are successful](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).

 It's recommended to run the `semantic-release` command in the [Travis `deploy` step](https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle) so if an error occurs the build will fail and Travis will send a notification.

 **Note**: It's not recommended to run the `semantic-release` command in the Travis `script` step as each script in this step will be executed regardless of the outcome of the previous one. See [travis-ci/travis-ci#1066](https://github.com/travis-ci/travis-ci/issues/1066).

+**Advanced configuration**: Running the tests in the `script` step of the `release` stage is not necessary as the previous stage(s) already ran them. To increase speed, the `script` step of the `release` stage can be overwritten to skip the tests. Note that other commands such as build or compilation might still be required.
+
 ```yaml
 language: go

@@ -112,18 +78,18 @@ go:
  - 1.6
  - 1.7

-os:
-  - linux
-  - osx
-
-deploy:
-  provider: script
-  skip_cleanup: true
-  script:
-    # Use nvm to install and use the Node LTS version (nvm is installed on all Travis images)
-    - nvm install lts/*
-    # Run semantic-release only on one job, after all other are successful
-    - npx travis-deploy-once "npx semantic-release"
+jobs:
+  include:
+    # Define the release stage that runs semantic-release
+    - stage: release
+      # Advanced: optionally overwrite your default `script` step to skip the tests
+      # script:
+      #   - make
+      deploy:
+        provider: script
+        skip_cleanup: true
+        script:
+          # Use nvm to install and use the Node LTS version (nvm is installed on all Travis images)
+          - nvm install lts/*
+          - npx semantic-release
 ```
-
-**Note**: See the `travis-deploy-once` [`pro`](https://github.com/semantic-release/travis-deploy-once#-p---pro) and [`travis-url`](https://github.com/semantic-release/travis-deploy-once#-u---travis-url) options for using with [Travis Pro](https://docs.travis-ci.com/user/travis-pro) and [Travis Enterprise](https://enterprise.travis-ci.com).
@@ -4,7 +4,7 @@

 **semantic-release** takes care of updating the `package.json`’s version before publishing to [npm](https://www.npmjs.com).

-By default, only the published package will contains the version, which is the only place where it is *really* required, but the updated `package.json` will not be pushed to the Git repository
+By default, only the published package will contain the version, which is the only place where it is *really* required, but the updated `package.json` will not be pushed to the Git repository

 However, the [`@semantic-release/git`](https://github.com/semantic-release/git) plugin can be used to push the updated `package.json` as well as other files to the Git repository.

@@ -145,7 +145,7 @@ If you have introduced a breaking bug in a release you have 2 options:

 In both cases **semantic-release** will publish a new release, so your package users' will get the fixed/reverted version.

-Depending on the package manager you are using, you might be able to un-publish or deprecate a release, in order to prevent users to download it by accident. For example npm allows you to [un-publish](https://docs.npmjs.com/cli/unpublish) in [next 72 hours](https://www.npmjs.com/policies/unpublish) after releasing or to [deprecate](https://docs.npmjs.com/cli/deprecate) a release.
+Depending on the package manager you are using, you might be able to un-publish or deprecate a release, in order to prevent users from downloading it by accident. For example npm allows you to [un-publish](https://docs.npmjs.com/cli/unpublish) [within 72 hours](https://www.npmjs.com/policies/unpublish) after releasing. You may also [deprecate](https://docs.npmjs.com/cli/deprecate) a release if you would rather avoid un-publishing.

 In any case **do not remove the Git tag associated with the buggy version**, otherwise **semantic-release** will later try to republish that version. Publishing a version after un-publishing is not supported by most package managers.

@@ -236,7 +236,7 @@ In addition the [verify conditions step](../../README.md#release-steps) verifies

 **semantic-release** is written using the latest [ECMAScript 2017](https://www.ecma-international.org/publications/standards/Ecma-262.htm) features, without transpilation which **requires Node version 8.3 or higher**.

-See [Node version requirement](../support/node-version.md#node-version-requirement) for more details and solutions.
+See [Node version requirement](./node-version.md#node-version-requirement) for more details and solutions.

 ## What is npx?

@@ -12,7 +12,7 @@ npm ERR! You do not have permission to publish "<package-name>". Are you logged

 This is most likely related to a misconfiguration of the [npm registry authentication](https://github.com/semantic-release/npm#npm-registry-authentication) or to your user [missing permission](https://docs.npmjs.com/cli/team) for publishing.

-It might also happen if the package name you are trying to publish already exists (in such case npm consider you are trying to publish a new version of a package that is not yours, hence the permission error).
+It might also happen if the package name you are trying to publish already exists (in the case of npm, you may be trying to publish a new version of a package that is not yours, hence the permission error).

 To verify if your package name is available you can use [npm-name-cli](https://github.com/sindresorhus/npm-name-cli):
 ```bash
@@ -2,12 +2,22 @@

 ## Run `semantic-release` only after all tests succeeded

-The `semantic-release` command must be executed only after all the tests in the CI build pass. If the build runs multiple jobs (for example to test on multiple Operating Systems or Node versions) the CI has to be configured to guarantee that the `semantic-release` command is executed only after all jobs are successful. This can be achieved with [Travis Build Stages](https://docs.travis-ci.com/user/build-stages), [CircleCI Workflows](https://circleci.com/docs/2.0/workflows), [Codeship Deployment Pipelines](https://documentation.codeship.com/basic/builds-and-configuration/deployment-pipelines), [GitLab Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html#introduction-to-pipelines-and-jobs), [Codefresh Pipelines](https://codefresh.io/docs/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines), [Wercker Workflows](http://devcenter.wercker.com/docs/workflows), [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline) or specific tools like [`travis-deploy-once`](https://github.com/semantic-release/travis-deploy-once).
+The `semantic-release` command must be executed only after all the tests in the CI build pass. If the build runs multiple jobs (for example to test on multiple Operating Systems or Node versions) the CI has to be configured to guarantee that the `semantic-release` command is executed only after all jobs are successful.
+Here is a few example of the CI services that can be used to achieve this:
+- [Travis Build Stages](https://docs.travis-ci.com/user/build-stages)
+- [CircleCI Workflows](https://circleci.com/docs/2.0/workflows)
+- [Codeship Deployment Pipelines](https://documentation.codeship.com/basic/builds-and-configuration/deployment-pipelines)
+- [GitLab Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html#introduction-to-pipelines-and-jobs)
+- [Codefresh Pipelines](https://codefresh.io/docs/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines)
+- [Wercker Workflows](http://devcenter.wercker.com/docs/workflows)
+- [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline).

 See [CI configuration recipes](../recipes/README.md#ci-configurations) for more details.

 ## Authentication

+### Push access to the remote repository
+
 **semantic-release** requires push access to the project Git repository in order to create [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging). The Git authentication can be set with one of the following environment variables:

 | Variable                        | Description                                                                                                                                                                                                                  |
@@ -19,6 +29,8 @@ See [CI configuration recipes](../recipes/README.md#ci-configurations) for more

 Alternatively the Git authentication can be set up via [SSH keys](../recipes/git-auth-ssh-keys.md).

+### Authentication for plugins
+
 Most **semantic-release** [plugins](plugins.md) require setting up authentication in order to publish to a package manager registry. The default [@semantic-release/npm](https://github.com/semantic-release/npm#environment-variables) and [@semantic-release/github](https://github.com/semantic-release/github#environment-variables) plugins require the following environment variables:

 | Variable    | Description                                                                                                                                                                                                                                                                                                               |
@@ -26,8 +38,10 @@ Most **semantic-release** [plugins](plugins.md) require setting up authenticatio
 | `NPM_TOKEN` | npm token created via [npm token create](https://docs.npmjs.com/getting-started/working_with_tokens#how-to-create-new-tokens).<br/>**Note**: Only the `auth-only` [level of npm two-factor authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication#levels-of-authentication) is supported. |
 | `GH_TOKEN`  | GitHub authentication token.<br/>**Note**: Only the [personal token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line) authentication is supported.                                                                                                                                 |

-See each plugin documentation for the environment variables to set up.
+See each plugin's documentation for the environment variables required.

 The authentication token/credentials have to be made available in the CI service via environment variables.

 See [CI configuration recipes](../recipes/README.md#ci-configurations) for more details on how to configure environment variables in your CI service.
+
+**Note**: The environment variables `GH_TOKEN`, `GITHUB_TOKEN`, `GL_TOKEN` and `GITLAB_TOKEN` can be used for both the Git authentication and the API authentication required by [@semantic-release/github](https://github.com/semantic-release/github) and [@semantic-release/gitlab](https://github.com/semantic-release/gitlab).
@@ -1,17 +1,17 @@
 # Configuration

 **semantic-release** configuration consists of:
- Git repository options ([URL](#repositoryurl), [release branch](#branch) and [tag format](#tagformat))
- [plugins](#plugins) definition
- run mode ([debug](#debug), [dry run](#dryrun) and [local (no CI)](#ci))
+- Git repository ([URL](#repositoryurl) and options [release branch](#branch) and [tag format](#tagformat))
+- Plugins [declaration](#plugins) and options
+- Run mode ([debug](#debug), [dry run](#dryrun) and [local (no CI)](#ci))

-All of these options can be configured directly or by extending a [shareable configuration](shareable-configurations.md).
+All of these options can be configured through config file, CLI arguments or by extending a [shareable configuration](shareable-configurations.md).

 Additionally, metadata of Git tags generated by **semantic-release** can be customized via standard [Git environment variables](#git-environment-variables).

 ## Configuration file

-**semantic-release**’s [options](#options), mode and [plugins](plugins.md) can be set via:
+**semantic-release**’s [options](#options), mode and [plugins](plugins.md) can be set via either:
 - A `.releaserc` file, written in YAML or JSON, with optional extensions: .`yaml`/`.yml`/`.json`/`.js`
 - A `release.config.js` file that exports an object
 - A `release` key in the project's `package.json` file
@@ -20,8 +20,7 @@ Alternatively, some options can be set via CLI arguments.

 The following three examples are the same.

-Via `release` key in the project's `package.json` file:
-
+- Via `release` key in the project's `package.json` file:
 ```json
 {
  "release": {
@@ -29,23 +28,15 @@ Via `release` key in the project's `package.json` file:
  }
 }
 ```
-```bash
-$ semantic-release
-```
-
-Via `.releaserc` file:

+- Via `.releaserc` file:
 ```json
 {
  "branch": "next"
 }
 ```
-```bash
-$ semantic-release
-```
-
-Via CLI argument:

+- Via CLI argument:
 ```bash
 $ semantic-release --branch next
 ```
@@ -133,6 +124,8 @@ CLI argument: `--debug`

 Output debugging information. This can also be enabled by setting the `DEBUG` environment variable to `semantic-release:*`.

+**Note**: The `debug` is used only supported via CLI argument. To enable debug mode from the [JS API](../developer-guide/js-api.md#javascript-api) use `require('debug').enable('semantic-release:*')`.
+
 ## Git environment variables

 | Variable              | Description                                                                                                                                                                                                                    | Default                              |
@@ -144,7 +137,8 @@ Output debugging information. This can also be enabled by setting the `DEBUG` en

 ## Existing version tags

-**semantic-release** uses [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging) to determine the commits added since the last release. If a release has been published before setting up **semantic-release** you must make sure the most recent commit included in the last published release is in the [release branch](#branch) history and is tagged with the version released, formatted according to the [tag format](#tagformat) configured (defaults to `vx.y.z`).
+**semantic-release** uses [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging) to determine the commits added since the last release.
+If a release has been published before setting up **semantic-release** you must make sure the most recent commit included in the last published release is in the [release branch](#branch) history and is tagged with the version released, formatted according to the [tag format](#tagformat) configured (defaults to `vx.y.z`).

 If the previous releases were published with [`npm publish`](https://docs.npmjs.com/cli/publish) this should already be the case.

@@ -1,10 +1,10 @@
 # Getting started

-In order to use **semantic-release** you must follows this steps:
- [Install](./installation.md#installation) **semantic-release** in your project
- Configure your Continuous Integration service to [run **semantic-release**](./ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded)
- Configure your Git repository and package manager repository [authentication](ci-configuration.md#authentication) in your Continuous Integration service
- Configure **semantic-release** [options and plugins](./configuration.md#configuration)
+In order to use **semantic-release** you must follow these steps:
+1. [Install](./installation.md#installation) **semantic-release** in your project
+2. Configure your Continuous Integration service to [run **semantic-release**](./ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded)
+3. Configure your Git repository and package manager repository [authentication](ci-configuration.md#authentication) in your Continuous Integration service
+4. Configure **semantic-release** [options and plugins](./configuration.md#configuration)

 Alternatively those steps can be easily done with the [**semantic-release** interactive CLI](https://github.com/semantic-release/cli):

@@ -19,4 +19,4 @@ semantic-release-cli setup

 See the [semantic-release-cli](https://github.com/semantic-release/cli#what-it-does) documentation for more details.

-**Note**: only a limited number of options, CI services and plugins is currently supported by `semantic-release-cli`.
+**Note**: only a limited number of options, CI services and plugins are currently supported by `semantic-release-cli`.
@@ -24,6 +24,6 @@ For other type of projects we recommend installing **semantic-release** directly
 $ npx semantic-release
 ```

-**Note:** For a global installation, it's recommended to specify the major **semantic-release** version to install (for example with with `npx semantic-release@15`, or `npm install -g semantic-release@15`). This way your build will not automatically use the next major **semantic-release** release that could possibly break your build. You will have to upgrade manually when a new major version is released.
+**Note**: For a global installation, it's recommended to specify the major **semantic-release** version to install (for example with with `npx semantic-release@15`). This way your build will not automatically use the next major **semantic-release** release that could possibly break your build. You will have to upgrade manually when a new major version is released.

-**Note:** `npx` is a tool bundled with `npm@>=5.2.0`. It is used to conveniently install the semantic-release binary and to execute it. See [What is npx](../support/FAQ.md#what-is-npx) for more details.
+**Note**: `npx` is a tool bundled with `npm@>=5.2.0`. It is used to conveniently install the semantic-release binary and to execute it. See [What is npx](../support/FAQ.md#what-is-npx) for more details.
@@ -17,25 +17,39 @@ A plugin is a npm module that can implement one or more of the following steps:

 **Note:** If no plugin with a `analyzeCommits` step is defined `@semantic-release/commit-analyzer` will be used.

-See [available plugins](../extending/plugins-list.md).
+## Plugins installation

-## Plugins configuration
+### Default plugins

-Each plugin must be installed and configured with the [`plugins` options](./configuration.md#plugins) by specifying the list of plugins by npm module name.
+These four plugins are already part of **semantic-release** and don't have to be installed separately:
+```
+"@semantic-release/commit-analyzer"
+"@semantic-release/github"
+"@semantic-release/npm"
+"@semantic-release/release-notes-generator"
+```
+
+### Additional plugins
+
+[Additional plugins](../extending/plugins-list.md) have to be installed via npm:

 ```bash
-$ npm install @semantic-release/commit-analyzer @semantic-release/release-notes-generator @semantic-release/npm -D
+$ npm install @semantic-release/git @semantic-release/changelog -D
 ```

+## Plugins declaration and execution order
+
+Each plugin must be configured with the [`plugins` options](./configuration.md#plugins) by specifying the list of plugins by npm module name.
+
 ```json
 {
  "plugins": ["@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/npm"]
 }
 ```

-## Plugin ordering
+**Note:** If the `plugins` option is defined, it overrides the default plugin list, rather than merging with it.

-For each [release step](../../README.md#release-steps) the plugins that implement that step will be executed in the order in which the are defined.
+For each [release step](../../README.md#release-steps) the plugins that implement that step will be executed in the order in which they are defined.

 ```json
 {
@@ -55,11 +69,11 @@ With this configuration **semantic-release** will:
 - execute the `generateNotes` implementation of `@semantic-release/release-notes-generator`
 - execute the `publish` implementation of `@semantic-release/npm`

-## Plugin options
+## Plugin options configuration

-A plugin options can specified by wrapping the name and an options object in an array. Options configured this way will be passed only to that specific plugin.
+A plugin configuration can be specified by wrapping the name and an options object in an array. Options configured this way will be passed only to that specific plugin.

-Global plugin options can defined at the root of the **semantic-release** configuration object. Options configured this way will be passed to all plugins.
+Global plugin configuration can be defined at the root of the **semantic-release** configuration object. Options configured this way will be passed to all plugins.

 ```json
 {
@@ -1,6 +1,6 @@
 # Shareable configurations

-A sharable configuration is an [npm](https://www.npmjs.com/) package that exports a **semantic-release** configuration object. It allows for use of the same configuration across several projects.
+A shareable configuration is an [npm](https://www.npmjs.com/) package that exports a **semantic-release** configuration object. It allows for use of the same configuration across several projects.

 The shareable configurations to use can be set with the [extends](configuration.md#extends) option.

@@ -1,3 +1,5 @@
+/* eslint require-atomic-updates: off */
+
 const {template, pick} = require('lodash');
 const marked = require('marked');
 const TerminalRenderer = require('marked-terminal');
@@ -46,12 +48,11 @@ async function run(context, plugins) {

  if (ciBranch !== options.branch) {
    logger.log(
-      `This test run was triggered on the branch ${ciBranch}, while semantic-release is configured to only publish from ${
-        options.branch
-      }, therefore a new version won’t be published.`
+      `This test run was triggered on the branch ${ciBranch}, while semantic-release is configured to only publish from ${options.branch}, therefore a new version won’t be published.`
    );
    return false;
  }
+
  logger[options.dryRun ? 'warn' : 'success'](
    `Run automated release from branch ${ciBranch}${options.dryRun ? ' in dry-run mode' : ''}`
  );
@@ -70,6 +71,7 @@ async function run(context, plugins) {
        );
        return false;
      }
+
      throw error;
    }
  } catch (error) {
@@ -92,6 +94,7 @@ async function run(context, plugins) {
    logger.log('There are no relevant changes, so no new version is released.');
    return false;
  }
+
  context.nextRelease = nextRelease;
  nextRelease.version = getNextVersion(context);
  nextRelease.gitTag = template(options.tagFormat)({version: nextRelease.version});
@@ -107,7 +110,7 @@ async function run(context, plugins) {
  } else {
    // Create the tag before calling the publish plugins as some require the tag to exists
    await tag(nextRelease.gitTag, {cwd, env});
-    await push(options.repositoryUrl, options.branch, {cwd, env});
+    await push(options.repositoryUrl, {cwd, env});
    logger.success(`Created tag ${nextRelease.gitTag}`);
  }

@@ -1,10 +1,9 @@
-const url = require('url');
 const {inspect} = require('util');
 const {toLower, isString} = require('lodash');
 const pkg = require('../../package.json');
 const {RELEASE_TYPE} = require('./constants');

-const homepage = url.format({...url.parse(pkg.homepage), hash: null});
+const [homepage] = pkg.homepage.split('#');
 const stringify = obj => (isString(obj) ? obj : inspect(obj, {breakLength: Infinity, depth: 2, maxArrayLength: 5}));
 const linkify = file => `${homepage}/blob/master/${file}`;

@@ -28,16 +27,17 @@ Please make sure to add the \`repositoryUrl\` to the [semantic-release configura
    )}).`,
  }),
  EGITNOPERMISSION: ({options}) => ({
-    message: 'The push permission to the Git repository is required.',
+    message: 'Cannot push to the Git repository.',
    details: `**semantic-release** cannot push the version tag to the branch \`${
      options.branch
-    }\` on remote Git repository with URL \`${options.repositoryUrl}\`.
+    }\` on the remote Git repository with URL \`${options.repositoryUrl}\`.

-Please refer to the [authentication configuration documentation](${linkify(
-      'docs/usage/ci-configuration.md#authentication'
-    )}) to configure the Git credentials on your CI environment and make sure the [repositoryUrl](${linkify(
-      'docs/usage/configuration.md#repositoryurl'
-    )}) is configured with a [valid Git URL](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols).`,
+This can be caused by:
+ - a misconfiguration of the [repositoryUrl](${linkify('docs/usage/configuration.md#repositoryurl')}) option
+ - the repository being unavailable
+ - or missing push permission for the user configured via the [Git credentials on your CI environment](${linkify(
+   'docs/usage/ci-configuration.md#authentication'
+ )})`,
  }),
  EINVALIDTAGFORMAT: ({tagFormat}) => ({
    message: 'Invalid `tagFormat` option.',
@@ -1,3 +1,5 @@
+/* eslint require-atomic-updates: off */
+
 const {isString, isPlainObject} = require('lodash');
 const {getGitHead} = require('../git');
 const hideSensitive = require('../hide-sensitive');
@@ -59,6 +61,7 @@ module.exports = {
          // Regenerate the release notes
          context.nextRelease.notes = await generateNotes(context);
        }
+
        // Call the next prepare plugin with the updated `nextRelease`
        return context;
      },
@@ -71,8 +74,8 @@ module.exports = {
    pipelineConfig: () => ({
      // Add `nextRelease` and plugin properties to published release
      transform: (release, step, {nextRelease}) => ({
-        ...(isPlainObject(release) ? release : {}),
-        ...nextRelease,
+        ...(release === false ? {} : nextRelease),
+        ...release,
        ...step,
      }),
    }),
@@ -27,6 +27,10 @@ module.exports = async (context, opts) => {

  // Merge config file options and CLI/API options
  let options = {...config, ...opts};
+  if (options.ci === false) {
+    options.noCi = true;
+  }
+
  const pluginsPath = {};
  let extendPaths;
  ({extends: extendPaths, ...options} = options);
@@ -81,6 +85,6 @@ module.exports = async (context, opts) => {
 };

 async function pkgRepoUrl(opts) {
-  const {pkg} = await readPkgUp(opts);
-  return pkg && (isPlainObject(pkg.repository) ? pkg.repository.url : pkg.repository);
+  const {packageJson} = (await readPkgUp(opts)) || {};
+  return packageJson && (isPlainObject(packageJson.repository) ? packageJson.repository.url : packageJson.repository);
 }
@@ -1,18 +1,8 @@
-const {parse, format} = require('url');
+const {parse, format} = require('url'); // eslint-disable-line node/no-deprecated-api
 const {isNil} = require('lodash');
 const hostedGitInfo = require('hosted-git-info');
 const {verifyAuth} = require('./git');

-const GIT_TOKENS = {
-  GIT_CREDENTIALS: undefined,
-  GH_TOKEN: undefined,
-  GITHUB_TOKEN: undefined,
-  GL_TOKEN: 'gitlab-ci-token:',
-  GITLAB_TOKEN: 'gitlab-ci-token:',
-  BB_TOKEN: 'x-token-auth:',
-  BITBUCKET_TOKEN: 'x-token-auth:',
-};
-
 /**
 * Determine the the git repository URL to use to push, either:
 * - The `repositoryUrl` as is if allowed to push
@@ -25,6 +15,18 @@ const GIT_TOKENS = {
 * @return {String} The formatted Git repository URL.
 */
 module.exports = async ({cwd, env, options: {repositoryUrl, branch}}) => {
+  const GIT_TOKENS = {
+    GIT_CREDENTIALS: undefined,
+    GH_TOKEN: undefined,
+    // GitHub Actions require the "x-access-token:" prefix for git access
+    // https://developer.github.com/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation
+    GITHUB_TOKEN: isNil(env.GITHUB_ACTION) ? undefined : 'x-access-token:',
+    GL_TOKEN: 'gitlab-ci-token:',
+    GITLAB_TOKEN: 'gitlab-ci-token:',
+    BB_TOKEN: 'x-token-auth:',
+    BITBUCKET_TOKEN: 'x-token-auth:',
+  };
+
  const info = hostedGitInfo.fromUrl(repositoryUrl, {noGitPlus: true});
  const {protocol, ...parsed} = parse(repositoryUrl);

@@ -39,12 +41,12 @@ module.exports = async ({cwd, env, options: {repositoryUrl, branch}}) => {
  // Test if push is allowed without transforming the URL (e.g. is ssh keys are set up)
  try {
    await verifyAuth(repositoryUrl, branch, {cwd, env});
-  } catch (error) {
+  } catch (_) {
    const envVar = Object.keys(GIT_TOKENS).find(envVar => !isNil(env[envVar]));
    const gitCredentials = `${GIT_TOKENS[envVar] || ''}${env[envVar] || ''}`;

    if (gitCredentials) {
-      // If credentials are set via anvironment variables, convert the URL to http/https and add basic auth, otherwise return `repositoryUrl` as is
+      // If credentials are set via environment variables, convert the URL to http/https and add basic auth, otherwise return `repositoryUrl` as is
      const [match, auth, host, path] = /^(?!.+:\/\/)(?:(.*)@)?(.*?):(.*)$/.exec(repositoryUrl) || [];
      return format({
        ...parse(match ? `ssh://${auth ? `${auth}@` : ''}${host}/${path}` : repositoryUrl),
@@ -28,7 +28,7 @@ module.exports = async ({cwd, env, options: {tagFormat}, logger}) => {
  // Generate a regex to parse tags formatted with `tagFormat`
  // by replacing the `version` variable in the template by `(.+)`.
  // The `tagFormat` is compiled with space as the `version` as it's an invalid tag character,
-  // so it's guaranteed to no be present in the `tagFormat`.
+  // so it's guaranteed to not be present in the `tagFormat`.
  const tagRegexp = `^${escapeRegExp(template(tagFormat)({version: ' '})).replace(' ', '(.+)')}`;
  const tags = (await getTags({cwd, env}))
    .map(tag => ({gitTag: tag, version: (tag.match(tagRegexp) || new Array(2))[1]}))
@@ -11,7 +11,7 @@ const debug = require('debug')('semantic-release:git');
 */
 async function getTagHead(tagName, execaOpts) {
  try {
-    return await execa.stdout('git', ['rev-list', '-1', tagName], execaOpts);
+    return (await execa('git', ['rev-list', '-1', tagName], execaOpts)).stdout;
  } catch (error) {
    debug(error);
  }
@@ -26,7 +26,7 @@ async function getTagHead(tagName, execaOpts) {
 * @throws {Error} If the `git` command fails.
 */
 async function getTags(execaOpts) {
-  return (await execa.stdout('git', ['tag'], execaOpts))
+  return (await execa('git', ['tag'], execaOpts)).stdout
    .split('\n')
    .map(tag => tag.trim())
    .filter(Boolean);
@@ -63,7 +63,7 @@ async function isRefInHistory(ref, execaOpts) {
 async function fetch(repositoryUrl, execaOpts) {
  try {
    await execa('git', ['fetch', '--unshallow', '--tags', repositoryUrl], execaOpts);
-  } catch (error) {
+  } catch (_) {
    await execa('git', ['fetch', '--tags', repositoryUrl], execaOpts);
  }
 }
@@ -75,8 +75,8 @@ async function fetch(repositoryUrl, execaOpts) {
 *
 * @return {String} the sha of the HEAD commit.
 */
-function getGitHead(execaOpts) {
-  return execa.stdout('git', ['rev-parse', 'HEAD'], execaOpts);
+async function getGitHead(execaOpts) {
+  return (await execa('git', ['rev-parse', 'HEAD'], execaOpts)).stdout;
 }

 /**
@@ -88,7 +88,7 @@ function getGitHead(execaOpts) {
 */
 async function repoUrl(execaOpts) {
  try {
-    return await execa.stdout('git', ['config', '--get', 'remote.origin.url'], execaOpts);
+    return (await execa('git', ['config', '--get', 'remote.origin.url'], execaOpts)).stdout;
  } catch (error) {
    debug(error);
  }
@@ -143,12 +143,11 @@ async function tag(tagName, execaOpts) {
 * Push to the remote repository.
 *
 * @param {String} repositoryUrl The remote repository URL.
- * @param {String} branch The branch to push.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 *
 * @throws {Error} if the push failed.
 */
-async function push(repositoryUrl, branch, execaOpts) {
+async function push(repositoryUrl, execaOpts) {
  await execa('git', ['push', '--tags', repositoryUrl], execaOpts);
 }

@@ -177,7 +176,7 @@ async function verifyTagName(tagName, execaOpts) {
 * @return {Boolean} `true` is the HEAD of the current local branch is the same as the HEAD of the remote branch, falsy otherwise.
 */
 async function isBranchUpToDate(branch, execaOpts) {
-  const remoteHead = await execa.stdout('git', ['ls-remote', '--heads', 'origin', branch], execaOpts);
+  const {stdout: remoteHead} = await execa('git', ['ls-remote', '--heads', 'origin', branch], execaOpts);
  try {
    return await isRefInHistory(remoteHead.match(/^(\w+)?/)[1], execaOpts);
  } catch (error) {
@@ -57,10 +57,12 @@ module.exports = (context, pluginsPath) => {
            plugin ? [plugin[0], Object.assign(plugin[1], options[type])] : plugin
          );
        }
+
        if (!validateStep({required}, options[type])) {
          errors.push(getError('EPLUGINCONF', {type, required, pluginConf: options[type]}));
          return pluginsConf;
        }
+
        pluginOpts = options[type];
      }

@@ -40,9 +40,11 @@ module.exports = (context, type, pluginOpt, pluginsPath) => {
        if (outputValidator && !outputValidator(result)) {
          throw getError(`E${type.toUpperCase()}OUTPUT`, {result, pluginName});
        }
+
        logger.success(`Completed step "${type}" of plugin "${pluginName}"`);
        return result;
      }
+
      logger.warn(`Skip step "${type}" of plugin "${pluginName}" in dry-run mode`);
    } catch (error) {
      logger.error(`Failed step "${type}" of plugin "${pluginName}"`);
@@ -4,7 +4,7 @@ const AggregateError = require('aggregate-error');
 const {extractErrors} = require('../utils');

 /**
- * A Function that execute a list of function sequencially. If at least one Function ins the pipeline throw an Error or rejects, the pipeline function rejects as well.
+ * A Function that execute a list of function sequencially. If at least one Function ins the pipeline throws an Error or rejects, the pipeline function rejects as well.
 *
 * @typedef {Function} Pipeline
 * @param {Any} input Argument to pass to the first step in the pipeline.
@@ -44,6 +44,7 @@ module.exports = (steps, {settleAll = false, getNextInput = identity, transform
          throw error;
        }
      }
+
      // Prepare input for the next step, passing the input of the last iteration (or initial parameter for the first iteration) and the result of the current one
      return getNextInput(lastInput, result);
    },
@@ -52,5 +53,6 @@ module.exports = (steps, {settleAll = false, getNextInput = identity, transform
  if (errors.length > 0) {
    throw new AggregateError(errors);
  }
+
  return results;
 };
@@ -12,6 +12,7 @@ const validateSteps = conf => {
    ) {
      return true;
    }
+
    conf = castArray(conf);

    if (conf.length !== 1) {
@@ -39,6 +40,7 @@ function validateStep({required}, conf) {
  if (required) {
    return conf.length >= 1 && validateSteps(conf);
  }
+
  return conf.length === 0 || validateSteps(conf);
 }

@@ -59,6 +61,7 @@ function parseConfig(plugin) {
  } else {
    path = plugin;
  }
+
  return [path, config || {}];
 }

@@ -3,17 +3,20 @@
  "description": "Automated semver compliant package publishing",
  "version": "0.0.0-development",
  "author": "Stephan Bönnemann <stephan@boennemann.me> (http://boennemann.me)",
+  "ava": {
+    "files": [
+      "test/**/*.test.js"
+    ],
+    "helpers": [
+      "test/helpers/**/*"
+    ]
+  },
  "bin": {
    "semantic-release": "bin/semantic-release.js"
  },
  "bugs": {
    "url": "https://github.com/semantic-release/semantic-release/issues"
  },
-  "config": {
-    "commitizen": {
-      "path": "cz-conventional-changelog"
-    }
-  },
  "contributors": [
    "Gregor Martynus (https://twitter.com/gr2m)",
    "Pierre Vanduynslager (https://twitter.com/@pvdlg_)"
@@ -24,49 +27,47 @@
    "@semantic-release/github": "^5.1.0",
    "@semantic-release/npm": "^5.0.5",
    "@semantic-release/release-notes-generator": "^7.1.2",
-    "aggregate-error": "^1.0.0",
+    "aggregate-error": "^3.0.0",
    "cosmiconfig": "^5.0.1",
    "debug": "^4.0.0",
-    "env-ci": "^3.0.0",
+    "env-ci": "^4.0.0",
    "execa": "^1.0.0",
-    "figures": "^2.0.0",
+    "figures": "^3.0.0",
    "find-versions": "^3.0.0",
-    "get-stream": "^4.0.0",
+    "get-stream": "^5.0.0",
    "git-log-parser": "^1.2.0",
-    "hook-std": "^1.1.0",
-    "hosted-git-info": "^2.7.1",
-    "lodash": "^4.17.4",
-    "marked": "^0.5.0",
-    "marked-terminal": "^3.0.0",
-    "p-locate": "^3.0.0",
-    "p-reduce": "^1.0.0",
-    "read-pkg-up": "^4.0.0",
-    "resolve-from": "^4.0.0",
-    "semver": "^5.4.1",
+    "hook-std": "^2.0.0",
+    "hosted-git-info": "^3.0.0",
+    "lodash": "^4.17.15",
+    "marked": "^0.7.0",
+    "marked-terminal": "^3.2.0",
+    "p-locate": "^4.0.0",
+    "p-reduce": "^2.0.0",
+    "read-pkg-up": "^7.0.0",
+    "resolve-from": "^5.0.0",
+    "semver": "^6.0.0",
    "signale": "^1.2.1",
-    "yargs": "^12.0.0"
+    "yargs": "^14.0.0"
  },
  "devDependencies": {
-    "ava": "^0.25.0",
-    "clear-module": "^3.0.0",
+    "ava": "^2.0.0",
+    "clear-module": "^4.0.0",
    "codecov": "^3.0.0",
-    "commitizen": "^3.0.0",
-    "cz-conventional-changelog": "^2.0.0",
    "delay": "^4.0.0",
-    "dockerode": "^2.5.2",
-    "file-url": "^2.0.2",
-    "fs-extra": "^7.0.0",
+    "dockerode": "^3.0.0",
+    "file-url": "^3.0.0",
+    "fs-extra": "^8.0.0",
    "got": "^9.0.0",
    "js-yaml": "^3.10.0",
    "mockserver-client": "^5.1.1",
-    "nock": "^10.0.0",
-    "nyc": "^12.0.1",
-    "p-retry": "^2.0.0",
+    "nock": "^11.1.0",
+    "nyc": "^14.0.0",
+    "p-retry": "^4.0.0",
    "proxyquire": "^2.0.0",
-    "sinon": "^6.0.0",
+    "sinon": "^7.2.7",
    "stream-buffers": "^3.0.2",
-    "tempy": "^0.2.1",
-    "xo": "^0.23.0"
+    "tempy": "^0.3.0",
+    "xo": "^0.25.0"
  },
  "engines": {
    "node": ">=8.3"
@@ -117,7 +118,6 @@
    "url": "git+https://github.com/semantic-release/semantic-release.git"
  },
  "scripts": {
-    "cm": "git-cz",
    "codecov": "codecov -f coverage/coverage-final.json",
    "lint": "xo",
    "pretest": "npm run lint",
@@ -66,7 +66,7 @@ test.serial('Pass options to semantic-release API', async t => {
  ];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.is(run.args[0][0].branch, 'master');
  t.is(run.args[0][0].repositoryUrl, 'https://github/com/owner/repo.git');
@@ -84,7 +84,7 @@ test.serial('Pass options to semantic-release API', async t => {
  t.is(run.args[0][0].debug, true);
  t.is(run.args[0][0].dryRun, true);

-  t.is(exitCode, 0);
+  t.is(code, 0);
 });

 test.serial('Pass options to semantic-release API with alias arguments', async t => {
@@ -108,7 +108,7 @@ test.serial('Pass options to semantic-release API with alias arguments', async t
  ];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.is(run.args[0][0].branch, 'master');
  t.is(run.args[0][0].repositoryUrl, 'https://github/com/owner/repo.git');
@@ -117,7 +117,7 @@ test.serial('Pass options to semantic-release API with alias arguments', async t
  t.deepEqual(run.args[0][0].extends, ['config1', 'config2']);
  t.is(run.args[0][0].dryRun, true);

-  t.is(exitCode, 0);
+  t.is(code, 0);
 });

 test.serial('Pass unknown options to semantic-release API', async t => {
@@ -125,13 +125,13 @@ test.serial('Pass unknown options to semantic-release API', async t => {
  const argv = ['', '', '--bool', '--first-option', 'value1', '--second-option', 'value2', '--second-option', 'value3'];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.is(run.args[0][0].bool, true);
  t.is(run.args[0][0].firstOption, 'value1');
  t.deepEqual(run.args[0][0].secondOption, ['value2', 'value3']);

-  t.is(exitCode, 0);
+  t.is(code, 0);
 });

 test.serial('Pass empty Array to semantic-release API for list option set to "false"', async t => {
@@ -139,11 +139,11 @@ test.serial('Pass empty Array to semantic-release API for list option set to "fa
  const argv = ['', '', '--publish', 'false'];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.deepEqual(run.args[0][0].publish, []);

-  t.is(exitCode, 0);
+  t.is(code, 0);
 });

 test.serial('Do not set properties in option for which arg is not in command line', async t => {
@@ -163,27 +163,15 @@ test.serial('Do not set properties in option for which arg is not in command lin
  t.false('e' in run.args[0][0]);
 });

-test.serial('Set "noCi" options to "true" with "--no-ci"', async t => {
-  const run = stub().resolves(true);
-  const argv = ['', '', '--no-ci'];
-  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});
-
-  const exitCode = await cli();
-
-  t.is(run.args[0][0].noCi, true);
-
-  t.is(exitCode, 0);
-});
-
 test.serial('Display help', async t => {
  const run = stub().resolves(true);
  const argv = ['', '', '--help'];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.regex(t.context.logs, /Run automated package publishing/);
-  t.is(exitCode, 0);
+  t.is(code, 0);
 });

 test.serial('Return error code and prints help if called with a command', async t => {
@@ -191,11 +179,11 @@ test.serial('Return error code and prints help if called with a command', async
  const argv = ['', '', 'pre'];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.regex(t.context.errors, /Run automated package publishing/);
  t.regex(t.context.errors, /Too many non-option arguments/);
-  t.is(exitCode, 1);
+  t.is(code, 1);
 });

 test.serial('Return error code if multiple plugin are set for single plugin', async t => {
@@ -203,11 +191,11 @@ test.serial('Return error code if multiple plugin are set for single plugin', as
  const argv = ['', '', '--analyze-commits', 'analyze1', 'analyze2'];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.regex(t.context.errors, /Run automated package publishing/);
  t.regex(t.context.errors, /Too many non-option arguments/);
-  t.is(exitCode, 1);
+  t.is(code, 1);
 });

 test.serial('Return error code if semantic-release throw error', async t => {
@@ -215,10 +203,10 @@ test.serial('Return error code if semantic-release throw error', async t => {
  const argv = ['', ''];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv}});

-  const exitCode = await cli();
+  const code = await cli();

  t.regex(t.context.errors, /semantic-release error/);
-  t.is(exitCode, 1);
+  t.is(code, 1);
 });

 test.serial('Hide sensitive environment variable values from the logs', async t => {
@@ -227,8 +215,8 @@ test.serial('Hide sensitive environment variable values from the logs', async t
  const argv = ['', ''];
  const cli = requireNoCache('../cli', {'.': run, process: {...process, argv, env: {...process.env, ...env}}});

-  const exitCode = await cli();
+  const code = await cli();

  t.regex(t.context.errors, new RegExp(`Throw error: Exposing token ${escapeRegExp(SECRET_REPLACEMENT)}`));
-  t.is(exitCode, 1);
+  t.is(code, 1);
 });
@@ -22,7 +22,7 @@ test('The "generateNotes" plugin output, if defined, must be a string', t => {
  t.true(plugins.generateNotes.outputValidator('string'));
 });

-test('The "publish" plugin output, if defined, must be an object', t => {
+test('The "publish" plugin output, if defined, must be an object or "false"', t => {
  t.false(plugins.publish.outputValidator(1));
  t.false(plugins.publish.outputValidator('string'));

@@ -30,6 +30,7 @@ test('The "publish" plugin output, if defined, must be an object', t => {
  t.true(plugins.publish.outputValidator());
  t.true(plugins.publish.outputValidator(null));
  t.true(plugins.publish.outputValidator(''));
+  t.true(plugins.publish.outputValidator(false));
 });

 test('The "generateNotes" plugins output are concatenated with separator and sensitive data is hidden', t => {
@@ -67,6 +67,18 @@ test('Default values, reading repositoryUrl (http url) from package.json if not
  t.is(result.tagFormat, `v\${version}`);
 });

+test('Convert "ci" option to "noCi"', async t => {
+  const pkg = {repository: 'https://host.null/owner/module.git', release: {ci: false}};
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  // Create package.json in repository root
+  await outputJson(path.resolve(cwd, 'package.json'), pkg);
+
+  const {options: result} = await t.context.getConfig({cwd});
+
+  t.is(result.noCi, true);
+});
+
 test('Read options from package.json', async t => {
  // Create a git repository, set the current working directory at the root of the repo
  const {cwd} = await gitRepo();
@@ -468,8 +480,8 @@ test('Throw an Error if one of the shareable config cannot be found', async t =>
  await outputJson(path.resolve(cwd, 'package.json'), {release: pkhOptions});
  await outputJson(path.resolve(cwd, 'shareable1.json'), options1);

-  const error = await t.throws(t.context.getConfig({cwd}), Error);
+  const error = await t.throwsAsync(t.context.getConfig({cwd}), Error);

-  t.is(error.message, "Cannot find module 'non-existing-path'");
+  t.regex(error.message, /Cannot find module 'non-existing-path'/);
  t.is(error.code, 'MODULE_NOT_FOUND');
 });
@@ -244,6 +244,19 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "BITB
  );
 });

+test('Return the "https" formatted URL if "GITHUB_ACTION" is set', async t => {
+  const {cwd} = await gitRepo();
+
+  t.is(
+    await getAuthUrl({
+      cwd,
+      env: {...env, GITHUB_ACTION: 'foo', GITHUB_TOKEN: 'token'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
+    }),
+    'https://x-access-token:token@host.null/owner/repo.git'
+  );
+});
+
 test('Handle "https" URL with group and subgroup, with "GIT_CREDENTIALS"', async t => {
  const {cwd} = await gitRepo();

@@ -42,7 +42,7 @@ test('Throw error if the last commit sha cannot be found', async t => {
  // Create a git repository, set the current working directory at the root of the repo
  const {cwd} = await gitRepo();

-  await t.throws(getGitHead({cwd}), Error);
+  await t.throwsAsync(getGitHead({cwd}), Error);
 });

 test('Unshallow and fetch repository', async t => {
@@ -67,7 +67,7 @@ test('Do not throw error when unshallow a complete repository', async t => {
  const {cwd, repositoryUrl} = await gitRepo();
  // Add commits to the master branch
  await gitCommits(['First'], {cwd});
-  await t.notThrows(fetch(repositoryUrl, {cwd}));
+  await t.notThrowsAsync(fetch(repositoryUrl, {cwd}));
 });

 test('Fetch all tags on a detached head repository', async t => {
@@ -100,7 +100,7 @@ test('Verify if the commit `sha` is in the direct history of the current branch'

  t.true(await isRefInHistory(commits[0].hash, {cwd}));
  t.falsy(await isRefInHistory(otherCommits[0].hash, {cwd}));
-  await t.throws(isRefInHistory('non-existant-sha', {cwd}));
+  await t.throwsAsync(isRefInHistory('non-existant-sha', {cwd}));
 });

 test('Get the commit sha for a given tag or falsy if the tag does not exists', async t => {
@@ -157,7 +157,7 @@ test('Push tag to remote repository', async t => {
  const commits = await gitCommits(['Test commit'], {cwd});

  await tag('tag_name', {cwd});
-  await push(repositoryUrl, 'master', {cwd});
+  await push(repositoryUrl, {cwd});

  t.is(await gitRemoteTagHead(repositoryUrl, 'tag_name', {cwd}), commits[0].hash);
 });
@@ -171,7 +171,7 @@ test('Push tag to remote repository with remote branch ahaed', async t => {
  await gitPush('origin', 'master', {cwd: tmpRepo});

  await tag('tag_name', {cwd});
-  await push(repositoryUrl, 'master', {cwd});
+  await push(repositoryUrl, {cwd});

  t.is(await gitRemoteTagHead(repositoryUrl, 'tag_name', {cwd}), commits[0].hash);
 });
@@ -206,7 +206,7 @@ test('Return falsy for invalid tag names', async t => {
 test('Throws error if obtaining the tags fails', async t => {
  const cwd = tempy.directory();

-  await t.throws(getTags({cwd}));
+  await t.throwsAsync(getTags({cwd}));
 });

 test('Return "true" if repository is up to date', async t => {
@@ -69,8 +69,10 @@ export async function initBareRepo(repositoryUrl, branch = 'master') {
 * @returns {Array<Commit>} The created commits, in reverse order (to match `git log` order).
 */
 export async function gitCommits(messages, execaOpts) {
-  await pReduce(messages, (_, message) =>
-    execa.stdout('git', ['commit', '-m', message, '--allow-empty', '--no-gpg-sign'], execaOpts)
+  await pReduce(
+    messages,
+    async (_, message) =>
+      (await execa('git', ['commit', '-m', message, '--allow-empty', '--no-gpg-sign'], execaOpts)).stdout
  );
  return (await gitGetCommits(undefined, execaOpts)).slice(0, messages.length);
 }
@@ -98,10 +100,10 @@ export async function gitGetCommits(from, execaOpts) {
 * Checkout a branch on the current git repository.
 *
 * @param {String} branch Branch name.
- * @param {Boolean} create `true` to create the branch, `false` to checkout an existing branch.
+ * @param {Boolean} create to create the branch, `false` to checkout an existing branch.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 */
-export async function gitCheckout(branch, create = true, execaOpts) {
+export async function gitCheckout(branch, create, execaOpts) {
  await execa('git', create ? ['checkout', '-b', branch] : ['checkout', branch], execaOpts);
 }

@@ -112,8 +114,8 @@ export async function gitCheckout(branch, create = true, execaOpts) {
 *
 * @return {String} The sha of the head commit in the current git repository.
 */
-export function gitHead(execaOpts) {
-  return execa.stdout('git', ['rev-parse', 'HEAD'], execaOpts);
+export async function gitHead(execaOpts) {
+  return (await execa('git', ['rev-parse', 'HEAD'], execaOpts)).stdout;
 }

 /**
@@ -181,8 +183,8 @@ export async function gitAddConfig(name, value, execaOpts) {
 *
 * @return {String} The sha of the commit associated with `tagName` on the local repository.
 */
-export function gitTagHead(tagName, execaOpts) {
-  return execa.stdout('git', ['rev-list', '-1', tagName], execaOpts);
+export async function gitTagHead(tagName, execaOpts) {
+  return (await execa('git', ['rev-list', '-1', tagName], execaOpts)).stdout;
 }

 /**
@@ -195,7 +197,7 @@ export function gitTagHead(tagName, execaOpts) {
 * @return {String} The sha of the commit associated with `tagName` on the remote repository.
 */
 export async function gitRemoteTagHead(repositoryUrl, tagName, execaOpts) {
-  return (await execa.stdout('git', ['ls-remote', '--tags', repositoryUrl, tagName], execaOpts))
+  return (await execa('git', ['ls-remote', '--tags', repositoryUrl, tagName], execaOpts)).stdout
    .split('\n')
    .filter(tag => Boolean(tag))
    .map(tag => tag.match(/^(\S+)/)[1])[0];
@@ -209,8 +211,8 @@ export async function gitRemoteTagHead(repositoryUrl, tagName, execaOpts) {
 *
 * @return {String} The tag associatedwith the sha in parameter or `null`.
 */
-export function gitCommitTag(gitHead, execaOpts) {
-  return execa.stdout('git', ['describe', '--tags', '--exact-match', gitHead], execaOpts);
+export async function gitCommitTag(gitHead, execaOpts) {
+  return (await execa('git', ['describe', '--tags', '--exact-match', gitHead], execaOpts)).stdout;
 }

 /**
@@ -222,6 +224,6 @@ export function gitCommitTag(gitHead, execaOpts) {
 *
 * @throws {Error} if the push failed.
 */
-export async function gitPush(repositoryUrl = 'origin', branch = 'master', execaOpts) {
+export async function gitPush(repositoryUrl, branch, execaOpts) {
  await execa('git', ['push', '--tags', repositoryUrl, `HEAD:${branch}`], execaOpts);
 }
@@ -1,16 +0,0 @@
-import nock from 'nock';
-
-/**
- * Retun a `nock` object setup to respond to a github authentication request. Other expectation and responses can be chained.
- *
- * @param {String} [githubToken='GH_TOKEN'] The github token to return in the authentication response.
- * @param {String} [githubUrl='https://api.github.com'] The url on which to intercept http requests.
- * @return {Object} A `nock` object ready to respond to a github authentication request.
- */
-export default function authenticate({
-  githubToken = 'GH_TOKEN',
-  githubUrl = 'https://api.github.com',
-  githubApiPathPrefix = '',
-} = {}) {
-  return nock(`${githubUrl}/${githubApiPathPrefix}`, {reqheaders: {Authorization: `token ${githubToken}`}});
-}
@@ -30,7 +30,7 @@ async function start() {
      minTimeout: 1000,
      factor: 2,
    });
-  } catch (error) {
+  } catch (_) {
    throw new Error(`Couldn't start mock-server after 2 min`);
  }
 }
@@ -39,7 +39,7 @@ async function start() {
      minTimeout: 1000,
      factor: 2,
    });
-  } catch (error) {
+  } catch (_) {
    throw new Error(`Couldn't start npm-registry-docker after 2 min`);
  }

@@ -169,7 +169,7 @@ test('Plugins are called with expected values', async t => {
  t.deepEqual(success.args[0][1].commits[0].message, commits[0].message);
  t.deepEqual(success.args[0][1].nextRelease, {...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`});
  t.deepEqual(success.args[0][1].releases, [
-    {...release1, ...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`, pluginName: '[Function: proxy]'},
+    {...release1, ...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`, pluginName: '[Function: functionStub]'},
    {...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`, pluginName: pluginNoop},
  ]);

@@ -178,7 +178,12 @@ test('Plugins are called with expected values', async t => {
    commits: [commits[0]],
    nextRelease: {...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`},
    releases: [
-      {...release1, ...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`, pluginName: '[Function: proxy]'},
+      {
+        ...release1,
+        ...nextRelease,
+        notes: `${notes1}\n\n${notes2}\n\n${notes3}`,
+        pluginName: '[Function: functionStub]',
+      },
      {...nextRelease, notes: `${notes1}\n\n${notes2}\n\n${notes3}`, pluginName: pluginNoop},
    ],
  });
@@ -337,15 +342,19 @@ test('Call all "success" plugins even if one errors out', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });

-  await t.throws(
+  await t.throwsAsync(
    semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
  );

  t.is(success1.callCount, 1);
-  t.deepEqual(success1.args[0][1].releases, [{...release, ...nextRelease, notes, pluginName: '[Function: proxy]'}]);
+  t.deepEqual(success1.args[0][1].releases, [
+    {...release, ...nextRelease, notes, pluginName: '[Function: functionStub]'},
+  ]);

  t.is(success2.callCount, 1);
-  t.deepEqual(success2.args[0][1].releases, [{...release, ...nextRelease, notes, pluginName: '[Function: proxy]'}]);
+  t.deepEqual(success2.args[0][1].releases, [
+    {...release, ...nextRelease, notes, pluginName: '[Function: functionStub]'},
+  ]);
 });

 test('Log all "verifyConditions" errors', async t => {
@@ -372,7 +381,7 @@ test('Log all "verifyConditions" errors', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
  const errors = [
-    ...(await t.throws(
+    ...(await t.throwsAsync(
      semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
    )),
  ];
@@ -417,7 +426,7 @@ test('Log all "verifyRelease" errors', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
  const errors = [
-    ...(await t.throws(
+    ...(await t.throwsAsync(
      semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
    )),
  ];
@@ -519,7 +528,7 @@ test('Dry-run skips fail', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
  const errors = [
-    ...(await t.throws(
+    ...(await t.throwsAsync(
      semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
    )),
  ];
@@ -693,7 +702,7 @@ test('Allow local releases with "noCi" option', async t => {
  t.is(success.callCount, 1);
 });

-test('Accept "undefined" value returned by the "generateNotes" plugins', async t => {
+test('Accept "undefined" value returned by "generateNotes" and "false" by "publish"', async t => {
  // Create a git repository, set the current working directory at the root of the repo
  const {cwd, repositoryUrl} = await gitRepo(true);
  // Add commits to the master branch
@@ -711,7 +720,8 @@ test('Accept "undefined" value returned by the "generateNotes" plugins', async t
  const generateNotes1 = stub().resolves();
  const notes2 = 'Release notes 2';
  const generateNotes2 = stub().resolves(notes2);
-  const publish = stub().resolves();
+  const publish = stub().resolves(false);
+  const success = stub().resolves();

  const options = {
    branch: 'master',
@@ -722,7 +732,7 @@ test('Accept "undefined" value returned by the "generateNotes" plugins', async t
    generateNotes: [generateNotes1, generateNotes2],
    prepare: stub().resolves(),
    publish,
-    success: stub().resolves(),
+    success,
    fail: stub().resolves(),
  };

@@ -754,6 +764,9 @@ test('Accept "undefined" value returned by the "generateNotes" plugins', async t
  t.is(publish.callCount, 1);
  t.deepEqual(publish.args[0][1].lastRelease, lastRelease);
  t.is(publish.args[0][1].nextRelease.notes, notes2);
+
+  t.is(success.callCount, 1);
+  t.deepEqual(success.args[0][1].releases, [{pluginName: '[Function: functionStub]'}]);
 });

 test('Returns false if triggered by a PR', async t => {
@@ -953,7 +966,7 @@ test('Log both plugins errors and errors thrown by "fail" plugin', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });

-  await t.throws(
+  await t.throwsAsync(
    semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
  );

@@ -978,7 +991,7 @@ test('Call "fail" only if a plugin returns a SemanticReleaseError', async t => {
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });

-  await t.throws(
+  await t.throwsAsync(
    semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
  );

@@ -995,7 +1008,7 @@ test('Throw SemanticReleaseError if repositoryUrl is not set and cannot be found
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
  const errors = [
-    ...(await t.throws(
+    ...(await t.throwsAsync(
      semanticRelease({}, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()})
    )),
  ];
@@ -1032,7 +1045,7 @@ test('Throw an Error if plugin returns an unexpected value', async t => {
    './lib/get-logger': () => t.context.logger,
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
-  const error = await t.throws(
+  const error = await t.throwsAsync(
    semanticRelease(options, {cwd, env: {}, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()}),
    Error
  );
@@ -1062,7 +1075,7 @@ test('Hide sensitive information passed to "fail" plugin', async t => {
    './lib/get-logger': () => t.context.logger,
    'env-ci': () => ({isCi: true, branch: 'master', isPr: false}),
  });
-  await t.throws(
+  await t.throwsAsync(
    semanticRelease(options, {cwd, env, stdout: new WritableStreamBuffer(), stderr: new WritableStreamBuffer()}),
    Error
  );
@@ -258,7 +258,7 @@ test('Exit with 1 if a plugin is not found', async t => {
    release: {analyzeCommits: 'non-existing-path', success: false, fail: false},
  });

-  const {code, stderr} = await t.throws(execa(cli, [], {env, cwd}));
+  const {code, stderr} = await t.throwsAsync(execa(cli, [], {env, cwd}));
  t.is(code, 1);
  t.regex(stderr, /Cannot find module/);
 });
@@ -276,7 +276,7 @@ test('Exit with 1 if a shareable config is not found', async t => {
    release: {extends: 'non-existing-path', success: false, fail: false},
  });

-  const {code, stderr} = await t.throws(execa(cli, [], {env, cwd}));
+  const {code, stderr} = await t.throwsAsync(execa(cli, [], {env, cwd}));
  t.is(code, 1);
  t.regex(stderr, /Cannot find module/);
 });
@@ -297,7 +297,7 @@ test('Exit with 1 if a shareable config reference a not found plugin', async t =
  });
  await writeJson(path.resolve(cwd, 'shareable.json'), shareable);

-  const {code, stderr} = await t.throws(execa(cli, [], {env, cwd}));
+  const {code, stderr} = await t.throwsAsync(execa(cli, [], {env, cwd}));
  t.is(code, 1);
  t.regex(stderr, /Cannot find module/);
 });
@@ -62,7 +62,7 @@ test('Wrap plugin in a function that add the "pluginName" to the error"', async
    './plugin-error': './test/fixtures',
  });

-  const error = await t.throws(plugin({options: {}}));
+  const error = await t.throwsAsync(plugin({options: {}}));

  t.is(error.pluginName, './plugin-error');
 });
@@ -72,7 +72,7 @@ test('Wrap plugin in a function that add the "pluginName" to multiple errors"',
    './plugin-errors': './test/fixtures',
  });

-  const errors = [...(await t.throws(plugin({options: {}})))];
+  const errors = [...(await t.throwsAsync(plugin({options: {}})))];
  for (const error of errors) {
    t.is(error.pluginName, './plugin-errors');
  }
@@ -107,7 +107,7 @@ test('Wrap "analyzeCommits" plugin in a function that validate the output of the
    {}
  );

-  const error = await t.throws(plugin({options: {}}));
+  const error = await t.throwsAsync(plugin({options: {}}));

  t.is(error.code, 'EANALYZECOMMITSOUTPUT');
  t.is(error.name, 'SemanticReleaseError');
@@ -125,7 +125,7 @@ test('Wrap "generateNotes" plugin in a function that validate the output of the
    {}
  );

-  const error = await t.throws(plugin({options: {}}));
+  const error = await t.throwsAsync(plugin({options: {}}));

  t.is(error.code, 'EGENERATENOTESOUTPUT');
  t.is(error.name, 'SemanticReleaseError');
@@ -143,7 +143,7 @@ test('Wrap "publish" plugin in a function that validate the output of the plugin
    {}
  );

-  const error = await t.throws(plugin({options: {}}));
+  const error = await t.throwsAsync(plugin({options: {}}));

  t.is(error.code, 'EPUBLISHOUTPUT');
  t.is(error.name, 'SemanticReleaseError');
@@ -255,6 +255,6 @@ test('Throws an error if the plugin is not found', t => {
    Error
  );

-  t.is(error.message, "Cannot find module 'non-existing-path'");
+  t.regex(error.message, /Cannot find module 'non-existing-path'/);
  t.is(error.code, 'MODULE_NOT_FOUND');
 });
@@ -83,7 +83,7 @@ test('Stop execution and throw error if a step rejects', async t => {
  const step2 = stub().rejects(new Error('test error'));
  const step3 = stub().resolves(3);

-  const error = await t.throws(pipeline([step1, step2, step3])(0), Error);
+  const error = await t.throwsAsync(pipeline([step1, step2, step3])(0), Error);
  t.is(error.message, 'test error');
  t.true(step1.calledWith(0));
  t.true(step2.calledWith(0));
@@ -98,7 +98,7 @@ test('Throw all errors from the first step throwing an AggregateError', async t
  const step2 = stub().rejects(new AggregateError([error1, error2]));
  const step3 = stub().resolves(3);

-  const errors = await t.throws(pipeline([step1, step2, step3])(0));
+  const errors = await t.throwsAsync(pipeline([step1, step2, step3])(0));

  t.deepEqual([...errors], [error1, error2]);
  t.true(step1.calledWith(0));
@@ -113,7 +113,7 @@ test('Execute all even if a Promise rejects', async t => {
  const step2 = stub().rejects(error1);
  const step3 = stub().rejects(error2);

-  const errors = await t.throws(pipeline([step1, step2, step3], {settleAll: true})(0));
+  const errors = await t.throwsAsync(pipeline([step1, step2, step3], {settleAll: true})(0));

  t.deepEqual([...errors], [error1, error2]);
  t.true(step1.calledWith(0));
@@ -129,7 +129,7 @@ test('Throw all errors from all steps throwing an AggregateError', async t => {
  const step1 = stub().rejects(new AggregateError([error1, error2]));
  const step2 = stub().rejects(new AggregateError([error3, error4]));

-  const errors = await t.throws(pipeline([step1, step2], {settleAll: true})(0));
+  const errors = await t.throwsAsync(pipeline([step1, step2], {settleAll: true})(0));

  t.deepEqual([...errors], [error1, error2, error3, error4]);
  t.true(step1.calledWith(0));
@@ -145,7 +145,7 @@ test('Execute each function in series passing a transformed input even if a step
  const step4 = stub().resolves(4);
  const getNextInput = (prevResult, result) => prevResult + result;

-  const errors = await t.throws(pipeline([step1, step2, step3, step4], {settleAll: true, getNextInput})(0));
+  const errors = await t.throwsAsync(pipeline([step1, step2, step3, step4], {settleAll: true, getNextInput})(0));

  t.deepEqual([...errors], [error2, error3]);
  t.true(step1.calledWith(0));
@@ -7,7 +7,7 @@ test('Throw a AggregateError', async t => {
  const {cwd} = await gitRepo();
  const options = {};

-  const errors = [...(await t.throws(verify({cwd, options})))];
+  const errors = [...(await t.throwsAsync(verify({cwd, options})))];

  t.is(errors[0].name, 'SemanticReleaseError');
  t.is(errors[0].code, 'ENOREPOURL');
@@ -27,7 +27,7 @@ test('Throw a SemanticReleaseError if does not run on a git repository', async t
  const cwd = tempy.directory();
  const options = {};

-  const errors = [...(await t.throws(verify({cwd, options})))];
+  const errors = [...(await t.throwsAsync(verify({cwd, options})))];

  t.is(errors[0].name, 'SemanticReleaseError');
  t.is(errors[0].code, 'ENOGITREPO');
@@ -39,7 +39,7 @@ test('Throw a SemanticReleaseError if the "tagFormat" is not valid', async t =>
  const {cwd, repositoryUrl} = await gitRepo(true);
  const options = {repositoryUrl, tagFormat: `?\${version}`};

-  const errors = [...(await t.throws(verify({cwd, options})))];
+  const errors = [...(await t.throwsAsync(verify({cwd, options})))];

  t.is(errors[0].name, 'SemanticReleaseError');
  t.is(errors[0].code, 'EINVALIDTAGFORMAT');
@@ -51,7 +51,7 @@ test('Throw a SemanticReleaseError if the "tagFormat" does not contains the "ver
  const {cwd, repositoryUrl} = await gitRepo(true);
  const options = {repositoryUrl, tagFormat: 'test'};

-  const errors = [...(await t.throws(verify({cwd, options})))];
+  const errors = [...(await t.throwsAsync(verify({cwd, options})))];

  t.is(errors[0].name, 'SemanticReleaseError');
  t.is(errors[0].code, 'ETAGNOVERSION');
@@ -63,7 +63,7 @@ test('Throw a SemanticReleaseError if the "tagFormat" contains multiple "version
  const {cwd, repositoryUrl} = await gitRepo(true);
  const options = {repositoryUrl, tagFormat: `\${version}v\${version}`};

-  const errors = [...(await t.throws(verify({cwd, options})))];
+  const errors = [...(await t.throwsAsync(verify({cwd, options})))];

  t.is(errors[0].name, 'SemanticReleaseError');
  t.is(errors[0].code, 'ETAGNOVERSION');
@@ -75,5 +75,5 @@ test('Return "true" if all verification pass', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
  const options = {repositoryUrl, tagFormat: `v\${version}`};

-  await t.notThrows(verify({cwd, options}));
+  await t.notThrowsAsync(verify({cwd, options}));
 });
Author	SHA1	Message	Date
knidarknessandPierre Vanduynslager	79d22a2556	fix: clarify message for EGITNOPERMISSION error	2019-10-09 17:57:18 -04:00
Pierre Vanduynslager	9f2ec79d67	docs: limit list of suggested tools for commit linting	2019-10-09 16:42:52 -04:00
greenkeeper[bot]andPierre Vanduynslager	0e24022608	fix(package): update read-pkg-up to version 7.0.0	2019-09-27 10:37:25 -07:00
greenkeeper[bot]andPierre Vanduynslager	5986bf920e	chore(package): update xo to version 0.25.0	2019-09-26 10:18:12 -07:00
greenkeeper[bot]andPierre Vanduynslager	c86045ca49	chore(package): update dockerode to version 3.0.0	2019-09-24 13:37:46 -07:00
Josh BiddickandGregor Martynus	9b78ab7c0d	docs: spelling (#1284 )	2019-09-05 15:01:13 -07:00
greenkeeper[bot]andGregor Martynus	8e4fa663fa	chore(package): update nock to version 11.1.0	2019-09-04 14:20:39 -07:00
Pierre Vanduynslager	6f33c76fde	docs: various clarifications and language improvvements	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	9fd93ac37a	docs: fix node version requirement link is FAQ	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	7ddc2cfcbc	docs: update table of content in `README.md` and in Gitbook `SUMMARY.md`	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	55c3616e3f	revert: docs(contributing): added instructions on how to run gitbook locally This reverts commit `a3da21a544`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	c517c7048e	revert: docs(contributing): copy/pasted "Use gitbook locally" instruction from original url This reverts commit `cd00c2dc86`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	4b13280713	docs: correct list of default plugins	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	95a9e89141	revert: fix(definitions): Repository documentation links This reverts commit `1eb302545e`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	54d8e3fe99	revert: docs: note publishing on distribution channels in beta This reverts commit `490d86d0d5`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	a6188d3902	revert: docs(recipes): cleaned doc and navigation This reverts commit `a8f8bffa37`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	e00b6c84df	revert: docs: repared broken links to "CI configuration recipes" This reverts commit `3f22978623`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	3c4a0fb773	revert: docs: cleaned "Developer guide" section navigation This reverts commit `b08486327d`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	e770c50f01	revert: docs: synched README.md and SUMMARY.md This reverts commit `813e5f65ed`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	5e41dc89bd	revert: docs: made doc file org clearer and augmented content This reverts commit `5a5eaec3da`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	ce3d1bc715	revert: docs: corrections and further clarifications This reverts commit `7cb5446bb5`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	58aaf057f6	revert: docs: update semantic-release-cli broken link This reverts commit `3bd63eb6a8`.	2019-08-22 14:47:21 -04:00
Pierre Vanduynslager	eea5de2863	revert: docs: broken link docs/03-recipes/travis.md This reverts commit `d2230fab7e`.	2019-08-22 14:47:21 -04:00
greenkeeper[bot]andPierre Vanduynslager	3c2fe35ded	fix(package): update yargs to version 14.0.0	2019-08-19 19:50:25 -04:00
Florian KellerandGregor Martynus	1eb302545e	fix(definitions): Repository documentation links	2019-08-16 10:17:24 -07:00
GoisandPierre Vanduynslager	d2230fab7e	docs: broken link docs/03-recipes/travis.md Fixed the link for `setup with semantic-release-cli.` in 'Environment Variables' section, refering a old file of this repo,	2019-08-13 14:15:28 -04:00
greenkeeper[bot]andGregor Martynus	391af986be	fix(package): update hosted-git-info to version 3.0.0	2019-08-12 11:21:36 -07:00
Crhistian RamirezandGregor Martynus	d45d8b6170	docs: fix typo	2019-08-11 09:32:29 -07:00
Pierre Vanduynslager	519df0d5c1	chore: remove commitizen from our dependencies	2019-08-09 14:13:09 -04:00
EmandGregor Martynus	e168802379	docs: tried to fix #1250	2019-08-05 21:19:32 -07:00
Alvaro Pinot @alvaropinotandGregor Martynus	3bd63eb6a8	docs: update semantic-release-cli broken link * Remove extra `01-`	2019-08-05 21:18:30 -07:00
Philipp RudloffandGregor Martynus	9a8a36ce45	fix(package): update dependency lodash to address security warnings (#1253 )	2019-08-05 21:17:22 -07:00
Emmanuel SciaraandGregor Martynus	7cb5446bb5	docs: corrections and further clarifications - (correction) removed comments from code samples. -(correction) remove recommendation for global install on CI environemnts. - Synched README.md and SUMMARY.md	2019-07-31 14:40:10 -07:00
Emmanuel SciaraandGregor Martynus	5a5eaec3da	docs: made doc file org clearer and augmented content This is a first step to improving the doc: - renamed directories; - augmented a fair bit of content. To be continued	2019-07-31 14:40:10 -07:00
Jed MaoandGregor Martynus	2d2bb38e61	docs(shareable-configurations-list): add `@jedmao/semantic-release-npm-github-config` (#1222 )	2019-07-31 08:57:19 -07:00
Emmanuel SciaraandGregor Martynus	cd00c2dc86	docs(contributing): copy/pasted "Use gitbook locally" instruction from original url	2019-07-30 17:44:23 -07:00
Emmanuel SciaraandGregor Martynus	a3da21a544	docs(contributing): added instructions on how to run gitbook locally	2019-07-30 17:44:23 -07:00
Emmanuel SciaraandGregor Martynus	813e5f65ed	docs: synched README.md and SUMMARY.md	2019-07-30 16:13:59 -07:00
Emmanuel SciaraandGregor Martynus	b08486327d	docs: cleaned "Developer guide" section navigation	2019-07-30 16:13:59 -07:00
Emmanuel SciaraandGregor Martynus	3f22978623	docs: repared broken links to "CI configuration recipes"	2019-07-30 16:13:59 -07:00
Emmanuel SciaraandGregor Martynus	a8f8bffa37	docs(recipes): cleaned doc and navigation Corrected inconsistancies between the sidebar and the actual pages. Remove non existing pages. Clarified status of "Package managers and languages" to "to be completed".	2019-07-30 16:13:59 -07:00
scott willekeandGregor Martynus	490d86d0d5	docs: note publishing on distribution channels in beta Since the readme hints at doing this, note that features to automate this are in beta. Also discussed at https://spectrum.chat/semantic-release/general/im-trying-to-configure-a-next-release~5bb8e692-a0cd-49be-8379-9fb6b25261fe	2019-07-21 19:03:45 -07:00
greenkeeper[bot]andGregor Martynus	665a582930	chore(package): update commitizen to version 4.0.0	2019-07-18 14:20:20 -07:00
David AghassiandGregor Martynus	9e28fd9da9	docs: added plugin developer guide docs	2019-07-18 14:20:11 -07:00
mehrad-rafighandGregor Martynus	6e60c58873	ci(node): set node 8 to node 8.3 and add node 12	2019-07-15 14:50:24 -07:00
greenkeeper[bot]andGregor Martynus	75f08302a9	fix(package): update marked to version 0.7.0	2019-07-06 10:15:52 -07:00
greenkeeper[bot]andGregor Martynus	4b2b2fb780	chore(package): update clear-module to version 4.0.0	2019-07-04 20:04:48 -07:00
Debjeet BiswasandGregor Martynus	3b8cae91fa	docs: fix typo fix misspelled `they`	2019-07-02 15:09:54 -07:00
Pierre Vanduynslager	6b3adf6bbe	fix: revert to execa `^1.0.0`	2019-06-26 12:33:59 -04:00
Rob CresswellandGregor Martynus	228fed7a0b	docs: document that plugins config is an override (#1216 ) This patch documents that the `plugin` config option is an override, not a merge with the default. This is significant, for example, if you customise the github plugin as it will then prevent npm publishing by default unless the npm plugin is also defined manually.	2019-06-25 13:01:55 -07:00
Pierre Vanduynslager	01a0b2d08a	test: use regexp to check missing module message	2019-06-25 11:30:37 -04:00
greenkeeper[bot]andPierre Vanduynslager	52c48be17b	fix(package): update execa to version 2.0.0	2019-06-25 11:30:37 -04:00
Pierre Vanduynslager	4ed6213977	style: fix prettier style	2019-06-07 11:47:28 -04:00
greenkeeper[bot]andPierre Vanduynslager	8051294ffd	fix(package): update env-ci to version 4.0.0	2019-06-07 11:21:44 -04:00
greenkeeper[bot]andPierre Vanduynslager	95a0456a85	chore(package): update ava to version 2.0.0	2019-06-05 14:43:18 -04:00
GregorandPierre Vanduynslager	038e640d5e	fix: prefix git auth with "x-access-token:" when run in a GitHub Action	2019-06-05 12:17:21 -04:00
GregorandPierre Vanduynslager	f3f9d1ef58	test: prefix git auth with "x-access-token:" when run in a GitHub Action	2019-06-05 12:17:21 -04:00
Johannes KleinandGregor Martynus	7e824b2c18	doc: add note to default plugins	2019-06-04 14:07:01 -07:00
Johannes KleinandGregor Martynus	d4520e10ed	doc: add info about default plugins	2019-06-04 14:07:01 -07:00
Niels HofmansandGregor Martynus	bcf3a853f2	docs:optimize images (#1185 ) *Total -- 258.67kb -> 182.47kb (29.46%) /media/semantic-release-cli.png -- 116.80kb -> 65.42kb (43.99%) /media/bender.png -- 141.88kb -> 117.05kb (17.5%)	2019-05-20 14:36:57 -07:00
Jan PiotrowskiandGregor Martynus	d034ce5249	docs: Remove broken waffle.io 💀 badge	2019-05-20 14:08:48 -07:00
greenkeeper[bot]andPierre Vanduynslager	74103abac4	fix(package): update read-pkg-up to version 6.0.0	2019-05-14 15:00:17 -04:00
greenkeeper[bot]andPierre Vanduynslager	6e64745f6b	chore(package): update fs-extra to version 8.0.0	2019-05-14 14:29:40 -04:00
Anton GolubandPierre Vanduynslager	4e001c34f9	docs: add `semantic-release-github-pages` to community plugins	2019-05-09 13:41:04 -04:00
Matt OakesandPierre Vanduynslager	edf382f888	docs: add `semantic-release-circleci-orb` to the community plugin list	2019-05-08 16:01:01 -04:00
Hannes RaboandPierre Vanduynslager	39d15b37f9	docs: add `semantic-release-slack-bot` to community plugins	2019-05-08 15:45:30 -04:00
greenkeeper[bot]andPierre Vanduynslager	079251c6b8	chore(package): update tempy to version 0.3.0	2019-05-08 15:13:27 -04:00
greenkeeper[bot]andPierre Vanduynslager	f4cf7c8b51	fix(package): update figures to version 3.0.0	2019-05-08 14:44:56 -04:00
Brett ZamirandPierre Vanduynslager	c8ec0fd67f	docs: fix grammar	2019-05-08 14:32:55 -04:00
greenkeeper[bot]andPierre Vanduynslager	1d776db143	chore(package): update nyc to version 14.0.0	2019-05-08 14:30:48 -04:00
Kengo TODAandPierre Vanduynslager	6b1938fd7e	docs: add a plugin for Gradle project	2019-04-15 13:32:14 -04:00
greenkeeper[bot]andPierre Vanduynslager	6f3c21a10e	fix(package): update resolve-from to version 5.0.0	2019-04-15 13:22:40 -04:00
greenkeeper[bot]andPierre Vanduynslager	06fe435254	fix(package): update aggregate-error to version 3.0.0	2019-04-15 11:38:39 -04:00
Ben HuttonandPierre Vanduynslager	61762e67a0	docs: update commitlint URL The current commitlint URL goes to a repo which contains a redirect message and new URL. Replace the outdated URL with the new URL for the commitlint repo.	2019-04-15 11:19:51 -04:00
greenkeeper[bot]andPierre Vanduynslager	5072fef3e4	chore(package): update file-url to version 3.0.0	2019-04-15 11:11:58 -04:00
greenkeeper[bot]andPierre Vanduynslager	d61e3bce2e	fix(package): update semver to version 6.0.0	2019-04-15 10:52:25 -04:00
Julien VialaandPierre Vanduynslager	0cd8a57b4f	docs: correct way to print release plugin name	2019-04-15 09:58:35 -04:00
greenkeeper[bot]andPierre Vanduynslager	db3fc3eaf7	fix(package): update hook-std to version 2.0.0	2019-04-13 23:57:25 -04:00
greenkeeper[bot]andPierre Vanduynslager	a90a1038e7	fix(package): update read-pkg-up to version 5.0.0	2019-03-21 12:09:56 -04:00
greenkeeper[bot]andPierre Vanduynslager	30723c5998	fix(package): update p-reduce to version 2.0.0	2019-03-13 13:23:05 -04:00
greenkeeper[bot]andPierre Vanduynslager	840af0d734	chore(package): update p-retry to version 4.0.0	2019-03-13 11:34:08 -04:00
greenkeeper[bot]andPierre Vanduynslager	0a584def20	fix(package): update get-stream to version 5.0.0	2019-03-13 11:22:34 -04:00
greenkeeper[bot]andPierre Vanduynslager	a5babc6157	fix(package): update p-locate to version 4.0.0	2019-03-13 11:02:21 -04:00
greenkeeper[bot]andPierre Vanduynslager	322c1c69ec	chore(package): update ava to version 1.3.1	2019-03-06 13:22:00 -05:00
greenkeeper[bot]andPierre Vanduynslager	20e5d83456	chore(package): update sinon to version 7.2.7	2019-03-04 13:21:34 -05:00
Nicolas DelperdangeandPierre Vanduynslager	e5a5867e82	docs(circle): fix incorrect script example Little mistake in the example to add a ssh key for circleCi	2019-03-04 12:13:08 -05:00
greenkeeper[bot]andPierre Vanduynslager	aed4ea2edc	fix(package): update yargs to version 13.1.0	2019-02-15 12:11:12 -05:00
greenkeeper[bot]andPierre Vanduynslager	448a0ff977	chore(package): update xo to version 0.24.0	2019-01-30 17:27:04 -05:00
Kevin LluchandPierre Vanduynslager	1b7d8b2d21	docs: add semantic-release-ado to community plugins	2019-01-29 16:15:23 -05:00
Austin Cawley-EdwardsandPierre Vanduynslager	952e3fdf64	docs: fix typo in CircleCI recipe	2019-01-22 11:32:41 -05:00
David AghassiandPierre Vanduynslager	6a8eede96f	docs: cleaned up wording and typos in docs	2019-01-12 14:27:56 -05:00
David AghassiandPierre Vanduynslager	4652cef1e6	docs: corrected typos in jsdocs	2019-01-12 14:27:56 -05:00
greenkeeper[bot]andPierre Vanduynslager	b7aeabad93	fix(package): update marked to version 0.6.0	2019-01-10 16:14:04 -05:00
greenkeeper[bot]andPierre Vanduynslager	3819ca56a9	chore(package): update ava to version 1.0.1	2018-12-27 14:43:11 -05:00
greenkeeper[bot]andPierre Vanduynslager	1aefd98d31	fix(package): update aggregate-error to version 2.0.0	2018-12-26 13:22:26 -05:00
Pierre Vanduynslager	1243f79064	fix: correctly handle skipped releases	2018-12-16 16:28:52 -05:00
Pierre Vanduynslager	70c68ef3ed	feat: allow `publish` plugins to return `false` in order to signify no release was done	2018-12-14 16:16:27 -05:00
Pierre VanduynslagerandGregor Martynus	048292baa5	docs: fix broken link in CircleCI recipe	2018-12-14 10:48:58 -08:00
Pierre VanduynslagerandGregor Martynus	0f642ffe4d	docs: remove mentions of `travis-deploy-once`	2018-12-14 10:48:58 -08:00
greenkeeper[bot]andPierre Vanduynslager	89ad3a0b61	chore(package): update p-retry to version 3.0.0	2018-12-12 11:59:37 -05:00
Pierre Vanduynslager	649b53087a	docs: mention that `debug` option is CLI only	2018-12-11 13:33:06 -05:00
Pierre Vanduynslager	862ec4c087	fix: allow to set `ci` option via API and config file	2018-12-11 13:33:06 -05:00
Pierre Vanduynslager	6b110b6e9e	docs: switch to spectrum.chat	2018-12-03 17:48:15 -05:00
Pierre Vanduynslager	e4c6649714	docs: syntax fixes in plugins list	2018-11-30 03:25:05 -05:00
Pierre Vanduynslager	6220641aba	docs: add `@semantic-release/apm` to plugins list	2018-11-30 03:25:05 -05:00
Evan SirokyandPierre Vanduynslager	a45273e921	docs: add maven-semantic-release to list of community plugins	2018-11-30 03:12:00 -05:00
Pierre Vanduynslager	d1091133b9	chore(package): update nyc and sinon	2018-11-30 02:10:04 -05:00
Pierre Vanduynslager	cd69583746	test: delete unused test helper file	2018-11-30 01:24:16 -05:00
Pierre Vanduynslager	ffe1062830	fix: remove unnecessary `branch` parameter from `push` function	2018-11-29 20:08:25 -05:00