docs: tried to fix #1250

docs: update semantic-release-cli broken link
* Remove extra `01-`
2019-08-05 21:19:32 -07:00 · 2019-08-05 21:18:30 -07:00 · 2019-08-05 21:17:22 -07:00 · 2019-07-31 14:40:10 -07:00 · 2019-07-31 14:40:10 -07:00 · 2019-07-31 08:57:19 -07:00
93 changed files with 1249 additions and 4514 deletions
@@ -1,3 +1,5 @@
+# Jetbrains IDEs
+.idea

 # Created by https://www.gitignore.io/api/macos,windows,linux,node

@@ -4,17 +4,15 @@ services:
  - docker

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

-# Trigger a push build on release and greenkeeper branches + PRs build on every branches
+# 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)
 branches:
  only:
    - master
-    - next
-    - beta
-    - /^\d+(.\d+)?.x$/
    - /^greenkeeper.*$/

 # Retry install on fail to avoid failing a build on network/disk/external errors
@@ -9,6 +9,7 @@ As a contributor, here are the guidelines we would like you to follow:
 - [Submitting a Pull Request](#submitting-a-pull-request)
 - [Coding rules](#coding-rules)
 - [Working with the code](#working-with-the-code)
+- [Working with the doc](#working-with-the-doc)

 We also recommend that you read [How to Contribute to Open Source](https://opensource.guide/how-to-contribute).

@@ -20,7 +21,7 @@ Help us keep **semantic-release** open and inclusive. Please read and follow our

 ### Improve documentation

-As a **semantic-release** user, you are the perfect candidate to help us improve our documentation: typo corrections, clarifications, more examples, new [recipes](docs/recipes/README.md), etc. Take a look at the [documentation issues that need help](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+user%3Asemantic-release+archived%3Afalse+label%3A%22help+wanted%22+label%3Adocs+).
+As a **semantic-release** user, you are the perfect candidate to help us improve our documentation: typo corrections, clarifications, more examples, new [recipes](docs/03-recipes/README.md), etc. Take a look at the [documentation issues that need help](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+user%3Asemantic-release+archived%3Afalse+label%3A%22help+wanted%22+label%3Adocs+).

 Please follow the [Documentation guidelines](#documentation).

@@ -36,7 +37,7 @@ Confirmed bugs and ready-to-implement features are marked with the [help wanted

 ## Using the issue tracker

-The issue tracker is the channel for [bug reports](#bug-report), [features requests](#feature-request) and [submitting pull requests](#submitting-a-pull-request) only. Please use the [Support](docs/support/README.md) and [Get help](README.md#get-help) sections for support, troubleshooting and questions.
+The issue tracker is the channel for [bug reports](#bug-report), [features requests](#feature-request) and [submitting pull requests](#submitting-a-pull-request) only. Please use the [Support](docs/05-support/README.md) and [Get help](README.md#get-help) sections for support, troubleshooting and questions.

 Before opening an issue or a Pull Request, please use the [GitHub issue search](https://github.com/issues?utf8=%E2%9C%93&q=user%3Asemantic-release) to make sure the bug or feature request hasn't been already reported or fixed.

@@ -50,7 +51,7 @@ Feature requests are welcome, but take a moment to find out whether your idea fi

 ### New plugin request

-[Plugins](docs/usage/plugins.md) are a great way to extend **semantic-release** capabilities, integrate with other systems and support new project type. Please provide as much detail and context as possible and fill the information requested in the [New plugin request template](https://github.com/semantic-release/semantic-release/issues/new?template=plugin-request.md).
+[Plugins](docs/01-usage/plugins.md) are a great way to extend **semantic-release** capabilities, integrate with other systems and support new project type. Please provide as much detail and context as possible and fill the information requested in the [New plugin request template](https://github.com/semantic-release/semantic-release/issues/new?template=plugin-request.md).

 ## Submitting a Pull Request

@@ -249,3 +250,41 @@ $ npm run test
 All the [semantic-release](https://github.com/semantic-release) repositories use [Commitizen](https://github.com/commitizen/cz-cli) to help you create [valid commit messages](#commit-message-guidelines).

 After staging your changes with `git add`, run `npm run cm` to start the interactive commit message CLI.
+
+## Working with the doc
+
+Working with the doc is like [working with the code](#working-with-the-code), with the difference that you might find useful to see your changes locally before submitting.
+
+You can do that by following the instructions below (copy/paste-ish from "[Use gitbook locally](https://til.secretgeek.net/gitbook/use_gitbook_locally.html)"):
+
+
+Install `gitbook-cli` globally:
+```
+$ npm install --global gitbook-cli
+```
+
+> **WARNING**: `gitbook-cli` will install the `gitbook` package when it is building the doc. If you have `gitbook` already installed, uninstall it first with a `npm uninstall -g gitbook` before installing `gitbook-cli`. 
+
+Once `gitbook-cli` is installed, from the root of the repo you're working on, you run...
+```
+$ gitbook build .
+Installing GitBook 3.2.3   # it installs the gitbook package automatically
+[..]
+```
+
+And it will generate a subfolder called `_book` which contains `index.html` and all the other html of the finished book. (You may want to add `_book` to your `.gitignore`)
+
+You can view that `_book\index.html` file directly in a browser, or serve the content locally from a mini webserver by running:
+```
+gitbook serve .
+```
+
+And then browse the result on the `port` 4000:
+```
+http://localhost:4000/
+```
+
+You can use a different `port` by using the `--port` argument, e.g. `gitbook serve . --port 4003`.
+
+You can output as `html`, `pdf`, `epub` or `mobi`. To find out how, use `gitbook help`.
+
@@ -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">
@@ -29,9 +24,6 @@
  <a href="https://www.npmjs.com/package/semantic-release">
    <img alt="npm next version" src="https://img.shields.io/npm/v/semantic-release/next.svg">
  </a>
-  <a href="https://www.npmjs.com/package/semantic-release">
-    <img alt="npm beta version" src="https://img.shields.io/npm/v/semantic-release/beta.svg">
-  </a>
 </p>

 **semantic-release** automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package.
@@ -47,11 +39,10 @@ This removes the immediate connection between human emotions and version numbers
 - New features and fixes are immediately available to users
 - Notify maintainers and users of new releases
 - Use formalized commit message convention to document changes in the codebase
- Publish on different distribution channels (such as [npm dist-tags](https://docs.npmjs.com/cli/dist-tag)) based on git merges
- Integrate with your [continuous integration workflow](docs/recipes/README.md#ci-configurations)
+- Integrate with your [continuous integration workflow](docs/03-recipes/README.md#ci-configurations)
 - Avoid potential errors associated with manual releases
- Support any [package managers and languages](docs/recipes/README.md#package-managers-and-languages) via [plugins](docs/usage/plugins.md)
- Simple and reusable configuration via [shareable configurations](docs/usage/shareable-configurations.md)
+- Support any [package managers and languages](docs/03-recipes/README.md#package-managers-and-languages) via [plugins](docs/01-usage/plugins.md)
+- Simple and reusable configuration via [shareable configurations](docs/01-usage/shareable-configurations.md)

 ## How does it work?

@@ -59,9 +50,9 @@ This removes the immediate connection between human emotions and version numbers

 **semantic-release** uses the commit messages to determine the type of changes in the codebase. Following formalized conventions for commit messages, **semantic-release** automatically determines the next [semantic version](https://semver.org) number, generates a changelog and publishes the release.

-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.
+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/01-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), [commitlint](https://github.com/conventional-changelog/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.

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

@@ -80,50 +71,55 @@ Here is an example of the release type that will be done based on a commit messa
 For each new commits added to the release branch (i.e. `master`) with `git push` or by merging a pull request or merging from another branch, a CI build is triggered and runs the `semantic-release` command to make a release if there are codebase changes since the last release that affect the package functionalities.

 If you need more control over the timing of releases you have a couple of options:
- Publish releases on a distribution channel (for example npm’s [dist-tags](https://docs.npmjs.com/cli/dist-tag)). This way you can keep control over what your users end up using by default, and you can decide when to make an automatically released version available to the stable channel, and promote it.
+- Publish releases on a distribution channel (for example npm’s [dist-tags](https://docs.npmjs.com/cli/dist-tag)). This way you can keep control over what your users end up using by default, and you can decide when to make an automatically released version available to the stable channel, and promote it. **NOTE**: `16.0.0-beta` of semantic-release, includes new features to automate the release of different branches to different npm distribution tags. The corresponding documentation can be found [on the beta branch of this repo](https://github.com/semantic-release/semantic-release/blob/beta/docs/recipes/distribution-channels.md#publishing-on-distribution-channels).
 - Develop on a `dev` branch and merge it to the release branch (i.e. `master`) once you are ready to publish. **semantic-release** will run only on pushes to the release branch.

 ### Release steps

 After running the tests, the command `semantic-release` will execute the following steps:

-| Step              | Description                                                                                                                     |
-|-------------------|---------------------------------------------------------------------------------------------------------------------------------|
-| Verify Conditions | Verify all the conditions to proceed with the release.                                                                          |
-| Get last release  | Obtain the commit corresponding to the last release by analyzing [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging). |
-| Analyze commits   | Determine the type of release based on the commits added since the last release.                                                |
-| Verify release    | Verify the release conformity.                                                                                                  |
-| Generate notes    | Generate release notes for the commits added since the last release.                                                            |
-| Create Git tag    | Create a Git tag corresponding to the new release version.                                                                      |
-| Prepare           | Prepare the release.                                                                                                            |
-| Publish           | Publish the release.                                                                                                            |
-| Notify            | Notify of new releases or errors.                                                                                               |
+| Step              | Step Hook            | Description                                                                                                                     |
+|-------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| Verify Conditions | `verifyConditions`   | Verify all the conditions to proceed with the release.                                                                          |
+| Get last release  | N/A                  | Obtain the commit corresponding to the last release by analyzing [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging). |
+| Analyze commits   | N/A                  | Determine the type of release based on the commits added since the last release.                                                |
+| Verify release    | `verifyRelease`      | Verify the release conformity.                                                                                                  |
+| Generate notes    | `generateNotes`      | Generate release notes for the commits added since the last release.                                                            |
+| Create Git tag    | N/A                  | Create a Git tag corresponding to the new release version.                                                                      |
+| Prepare           | `prepare`            | Prepare the release.                                                                                                            |
+| Publish           | `publish`            | Publish the release.                                                                                                            |
+| Notify            | `success`, `failure` | Notify of new releases or errors.                                                                                               |

 ## Documentation

 - 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)
-  - [Plugins](docs/usage/plugins.md)
-  - [Shareable configurations](docs/usage/shareable-configurations.md)
+  - [Getting started](docs/01-usage/getting-started.md)
+  - [Installation](docs/01-usage/installation.md#installation)
+  - [CI Configuration](docs/01-usage/ci-configuration.md#ci-configuration)
+  - [Configuration](docs/01-usage/configuration.md#configuration)
+  - [Plugins](docs/01-usage/plugins.md)
+  - [Shareable configurations](docs/01-usage/shareable-configurations.md)
 - Extending
-  - [Plugins](docs/extending/plugins-list.md)
-  - [Shareable configuration](docs/extending/shareable-configurations-list.md)
+  - [Available plugins](docs/02-extending/plugins-list.md)
+  - [Available shareable configuration](docs/02-extending/shareable-configurations-list.md)
 - Recipes
-  - [CI configurations](docs/recipes/README.md)
-  - [Package managers and languages](docs/recipes/README.md)
+  - [CI pipelines recipes](docs/03-recipes/ci-pipelines-recipes.md)
+    - [CircleCI 2.0 workflows](docs/03-recipes/circleci-workflows.md)
+    - [Travis CI](docs/03-recipes/travis.md)
+    - [GitLab CI](docs/03-recipes/gitlab-ci.md)
+  - [Git hosted services](docs/03-recipes/git-hosted-services.md)
+    - [Git authentication with SSH keys](docs/03-recipes/git-auth-ssh-keys.md)
+  - [Package managers and languages](docs/03-recipes/package-managers-and-languages.md)
 - Developer guide
-  - [JavaScript API](docs/developer-guide/js-api.md)
-  - [Plugins](docs/developer-guide/plugin.md)
-  - [Shareable configuration](docs/developer-guide/shareable-configuration.md)
+  - [JavaScript API](docs/04-developer-guide/js-api.md)
+  - [Plugin development](docs/04-developer-guide/plugin.md)
+  - [Shareable configuration development](docs/04-developer-guide/shareable-configuration.md)
 - Support
-  - [Resources](docs/support/resources.md)
-  - [Frequently Asked Questions](docs/support/FAQ.md)
-  - [Troubleshooting](docs/support/troubleshooting.md)
-  - [Node version requirement](docs/support/node-version.md)
-  - [Node Support Policy](docs/support/node-support-policy.md)
+  - [Resources](docs/05-support/resources.md)
+  - [Frequently Asked Questions](docs/05-support/FAQ.md)
+  - [Troubleshooting](docs/05-support/troubleshooting.md)
+  - [Node version requirement](docs/05-support/node-version.md)
+  - [Node Support Policy](docs/05-support/node-support-policy.md)

 ## Get help

@@ -1,34 +1,34 @@
 # Summary

 ## Usage
- [Installation](docs/usage/installation.md#installation)
- [CI Configuration](docs/usage/ci-configuration.md#ci-configuration)
- [Configuration](docs/usage/configuration.md#configuration)
- [Plugins](docs/usage/plugins.md)
- [Shareable configurations](docs/usage/shareable-configurations.md)
+- [Getting started](docs/01-usage/getting-started.md)
+- [Installation](docs/01-usage/installation.md#installation)
+- [CI Configuration](docs/01-usage/ci-configuration.md#ci-configuration)
+- [Configuration](docs/01-usage/configuration.md#configuration)
+- [Plugins](docs/01-usage/plugins.md)
+- [Shareable configurations](docs/01-usage/shareable-configurations.md)

-## Extending
- [Plugins](docs/extending/plugins-list.md)
- [Shareable configuration](docs/extending/shareable-configurations-list.md)
+## Extensions
+- [Available plugins](docs/02-extending/plugins-list.md)
+- [Available shareable configuration](docs/02-extending/shareable-configurations-list.md)

 ## Recipes
- [CI configurations](docs/recipes/README.md)
-	- [CircleCI 2.0 workflows](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 authentication with SSH keys](docs/recipes/git-auth-ssh-keys.md)
- [Package managers and languages](docs/recipes/README.md)
+- [CI pipelines recipes](docs/03-recipes/ci-pipelines-recipes.md)
+  - [CircleCI 2.0 workflows](docs/03-recipes/circleci-workflows.md)
+  - [Travis CI](docs/03-recipes/travis.md)
+  - [GitLab CI](docs/03-recipes/gitlab-ci.md)
+- [Git hosted services](docs/03-recipes/git-hosted-services.md)
+  - [Git authentication with SSH keys](docs/03-recipes/git-auth-ssh-keys.md)
+- [Package managers and languages](docs/03-recipes/package-managers-and-languages.md)

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

 ## Support
- [Resources](docs/support/resources.md)
- [Frequently Asked Questions](docs/support/FAQ.md)
- [Troubleshooting](docs/support/troubleshooting.md)
- [Node version requirement](docs/support/node-version.md)
- [Node Support Policy](docs/support/node-support-policy.md)
+- [Resources](docs/05-support/resources.md)
+- [Frequently Asked Questions](docs/05-support/FAQ.md)
+- [Troubleshooting](docs/05-support/troubleshooting.md)
+- [Node version requirement](docs/05-support/node-version.md)
+- [Node Support Policy](docs/05-support/node-support-policy.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');

@@ -19,7 +19,7 @@ module.exports = async () => {
 Usage:
  semantic-release [options] [plugins]`);
    })
-    .option('b', {alias: 'branches', describe: 'Git branches to release from', ...stringList, group: 'Options'})
+    .option('b', {alias: 'branch', describe: 'Git branch to release from', type: 'string', group: 'Options'})
    .option('r', {alias: 'repository-url', describe: 'Git repository URL', type: 'string', group: 'Options'})
    .option('t', {alias: 'tag-format', describe: 'Git tag format', type: 'string', group: 'Options'})
    .option('p', {alias: 'plugins', describe: 'Plugins', ...stringList, group: 'Options'})
@@ -51,12 +51,14 @@ Usage:
      // 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;
  }
 };
@@ -1,14 +1,29 @@
 # CI configuration

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

-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) or [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline).
+The `semantic-release` command will only run fully in a CI environment. If it does not detect that it is in a CI environment, it will automatically run in `dry-run` mode.
+ 
+Within a CI environment, the `semantic-release` command must be executed only after all the tests in the CI build pass, otherwise it will release potentially faulty code. 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. 

-See [CI configuration recipes](../recipes/README.md#ci-configurations) for more details.
+Follow the CI system's documentation to find out how to do 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).
+
+This documentation provides a few [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details.

 ## Authentication

-**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:
+### Push access to remote repos
+
+**semantic-release** requires push access to remote Git repositories in order to push the [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging) it created.
+
+The Git authentication can be set with one of the following environment variables:

 | Variable                        | Description                                                                                                                                                                                                                  |
 |---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -17,17 +32,22 @@ See [CI configuration recipes](../recipes/README.md#ci-configurations) for more
 | `BB_TOKEN` or `BITBUCKET_TOKEN` | A Bitbucket [personal access token](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html).                                                                                                 |
 | `GIT_CREDENTIALS`               | [URL encoded](https://en.wikipedia.org/wiki/Percent-encoding) Git username and password in the format `<username>:<password>`. The username and password must each be individually URL encoded, not the `:` separating them. |

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

-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:
+### Authentication needs for plugins
+
+Most **semantic-release** [plugins](plugins.md) require setting up authentication in order to publish to a package manager registry. See each plugin's documentation for the environment variables required.
+
+It is to note, however, that:
+- The default [@semantic-release/github](https://github.com/semantic-release/github#environment-variables) plugin requires the same `GH_TOKEN` environment variable as above
+- The default [@semantic-release/npm](https://github.com/semantic-release/npm#environment-variables) plugin requires the following environment variables:

 | Variable    | Description                                                                                                                                                                                                                                                                                                               |
 |-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `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 authentication token/credentials have to be made available in the CI service via environment variables.
+>
+> See [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details on how to configure environment variables in your CI service.
@@ -1,91 +1,108 @@
 # Configuration

 **semantic-release** configuration consists of:
- Git repository options ([URL](#repositoryurl), [release branches](#branches) 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)). ([Access credentials](ci-configuration.md) are setup through environment variables)
+- Plugins [declaration](#plugins) and [options](plugins.md).
+- Run mode ([`--dry-run`](#dryrun), [`--no-ci`](#ci) (local), [`--debug`](#debug)).

-All of these options can be configured directly or by extending a [shareable configuration](shareable-configurations.md).
+All of these options can be configured:
+- In a config file.
+- Through the cli.
+- 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
+## Configuring/passing options to `semantic-release`

-**semantic-release**’s [options](#options), mode and [plugins](plugins.md) can be set via:
- 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
+### Configuration file

-Alternatively, some options can be set via CLI arguments.
+> **Note**: CLI arguments take precedence over options configured in the configuration file and shareable configuration.

-The following three examples are the same.
+**semantic-release**’s options, mode and plugins can be set via a config file in different ways:
+- A `.releaserc` file, written in YAML or JSON, with optional extensions `.yaml`, `.yml`, `.json` or `.js`.
+- A `release.config.js` file that exports an object.
+- A `release` key in the project's `package.json` file.

-Via `release` key in the project's `package.json` file:
+The following two examples are the same:
+- Via `.releaserc` or `release.config.js` file:    
+    ```json
+    {
+      "branch": "next"
+    }
+    ```
+- Via `release` key in the project's `package.json` file (the configuration must be under the `release` property):
+    ```json
+    {
+      "release": {
+        "branch": "next"
+      }
+    }
+    ```

-```json
-{
-  "release": {
-    "branches": ["master", "next"]
-  }
-}
-```
-```bash
-$ semantic-release
-```
+### Using CLI arguments

-Via `.releaserc` file:
+> **Note**: CLI arguments take precedence over options configured in the configuration file and shareable configuration.

-```json
-{
-  "branches": ["master", "next"]
-}
-```
-```bash
-$ semantic-release
-```
+Plugin options cannot be defined via CLI arguments and must be defined in the configuration file.

-Via CLI argument:
+The following configuration example via CLI argument is equivalent to the configuration file's example:

 ```bash
 $ semantic-release --branch next
 ```

-**Note**: CLI arguments take precedence over options configured in the configuration file.
+### Extending a shareable configuration

-**Note**: Plugin options cannot be defined via CLI arguments and must be defined in the configuration file.
+> **Note**: CLI arguments take precedence over options configured in the configuration file and shareable configuration.

-**Note**: When configuring via `package.json`, the configuration must be under the `release` property. However, when using a `.releaserc` or a `release.config.js` file, the configuration must be set without a `release` property.
+Please see [shareable configuration](shareable-configurations.md) for more details.

 ## Options

-### extends
+### `extends`

 Type: `Array`, `String`<br>
 CLI arguments: `-e`, `--extends`

-List of modules or file paths containing a [shareable configuration](shareable-configurations.md). If multiple shareable configurations are set, they will be imported in the order defined with each configuration option taking precedence over the options defined in a previous shareable configuration.
+Contains a list of:
+- Modules.
+- File paths containing a [shareable configuration](shareable-configurations.md). 

-**Note**: Options defined via CLI arguments or in the configuration file will take precedence over the ones defined in any shareable configuration.
+> **Note**:  If multiple shareable configurations are set, they will be imported **in the order defined with each configuration option** taking precedence over the options defined in a previous shareable configuration.

-### branches
+Examples (`.releaserc` file content):
+- `Array`:
+    ```json
+    {
+      "extends": [
+        "./my_config_dir/my.config",
+        "@semantic-release/gitlab-config",
+      ]
+    }
+    ```
+- `String`:
+    ```json
+    {
+      "extends": "@semantic-release/gitlab-config"
+    }
+    ```

-Type: `Array`, `String`, `Object`<br>
-Default: `['+([1-9])?(.{+([1-9]),x}).x', 'master', 'next', 'next-major', {name: 'beta', prerelease: true}, {name: 'alpha', prerelease: true}]`<br>
-CLI arguments: `--branches`
+### `branch`

-The branches on which releases should happen. By default **semantic-release** will release:
- regular releases to the default distribution channel from the branch `master`
- regular releases to a distribution channel matching the branch name from any existing branch with a name matching a maintenance release range (`N.N.x` or `N.x.x` or `N.x` with `N` being a number)
- regular releases to the `next` distribution channel from the branch `next` if it exists
- regular releases  to the `next-major` distribution channel from the branch `next-major` if it exists
- prereleases to the `beta` distribution channel from the branch `beta` if it exists
- prereleases to the `alpha` distribution channel from the branch `alpha` if it exists
+Type: `String`<br>
+Default: `master`<br>
+CLI arguments: `-b`, `--branch`

-**Note**: Once **semantic-release** is configured, any user with the permission to push commits on one of those branches will be able to publish a release. It is recommended to protect those branches, for example with [GitHub protected branches](https://help.github.com/articles/about-protected-branches).
+The branch on which releases should happen.

-See [Plugins configuration](plugins.md#plugins) for more details.
+Example (`.releaserc` file content):
+```json
+{
+  "branch": "next"
+}
+```

-### repositoryUrl
+### `repositoryUrl`

 Type: `String`<br>
 Default: `repository` property in `package.json` or [git origin url](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes)<br>
@@ -95,7 +112,14 @@ The git repository URL.

 Any valid git url format is supported (See [Git protocols](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols)).

-### tagFormat
+Example (`.releaserc` file content):
+```json
+{
+  "repositoryUrl": "https://github.com/username/project.git"
+}
+```
+
+### `tagFormat`

 Type: `String`<br>
 Default: `v${version}`<br>
@@ -103,21 +127,41 @@ CLI arguments: `-t`, `--tag-format`

 The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) format used by **semantic-release** to identify releases. The tag name is generated with [Lodash template](https://lodash.com/docs#template) and will be compiled with the `version` variable.

-**Note**: The `tagFormat` must contain the `version` variable exactly once and compile to a [valid Git reference](https://git-scm.com/docs/git-check-ref-format#_description).
+> **Note**: The `tagFormat` must contain the `version` variable exactly once and compile to a [valid Git reference](https://git-scm.com/docs/git-check-ref-format#_description).

-### plugins
+Example (`.releaserc` file content):
+```json
+{
+  "tagFormat": "version-${version}"
+}
+```
+
+### `plugins`

 Type: `Array`<br>
 Default: `['@semantic-release/commit-analyzer', '@semantic-release/release-notes-generator', '@semantic-release/npm', '@semantic-release/github']`<br>
 CLI arguments: `-p`, `--plugins`

-Define the list of plugins to use. Plugins will run in series, in the order defined, for each [steps](../../README.md#release-steps) if they implement it.
+Define the list of plugins to use. Plugins will run in series, **in the order defined**, for **each [steps](../../README.md#release-steps)** if they implement it.

-Plugins configuration can defined by wrapping the name and an options object in an array.
+Plugin specific configuration can defined by wrapping the name and an options object in an array. See [Plugins configuration options](plugins.md#plugins-configuration-options) for more details.

-See [Plugins configuration](plugins.md#plugins) for more details.
-
-### dryRun
+Example (`.releaserc` file content):
+```json
+{
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    "@semantic-release-docker",
+    ["@semantic-release/exec", {
+      "verifyConditionsCmd": "./verify.sh"
+    }],
+    "@semantic-release/git",
+    "@semantic-release/gitlab",
+  ]
+}
+```
+### `dryRun`

 Type: `Boolean`<br>
 Default: `false` if running in a CI environment, `true` otherwise<br>
@@ -125,7 +169,14 @@ CLI arguments: `-d`, `--dry-run`

 Dry-run mode, skip publishing, print next version and release notes.

-### ci
+Example (`.releaserc` file content):
+```json
+{
+  "dryRun": "true"
+}
+```
+
+### `ci`

 Type: `Boolean`<br>
 Default: `true`<br>
@@ -133,9 +184,16 @@ CLI arguments: `--ci` / `--no-ci`

 Set to `false` to skip Continuous Integration environment verifications. This allows for making releases from a local machine.

-**Note**: The CLI arguments `--no-ci` is equivalent to `--ci false`.
+> **Note**: The CLI arguments `--no-ci` is equivalent to `--ci false`.

-### debug
+Example (`.releaserc` file content):
+```json
+{
+  "ci": "false"
+}
+```
+
+### `debug` (only through CLI)

 Type: `Boolean`<br>
 Default: `false`<br>
@@ -143,7 +201,12 @@ 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:*')`.
+> **Note**: The `debug` is used only supported via CLI argument. To enable debug mode from the [JS API](../04-developer-guide/js-api.md#javascript-api) use `require('debug').enable('semantic-release:*')`.
+
+Example:
+```bash
+$ semantic-release --debug
+```

 ## Git environment variables

@@ -154,9 +217,11 @@ Output debugging information. This can also be enabled by setting the `DEBUG` en
 | `GIT_COMMITTER_NAME`  | The committer name associated with the [Git release tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging). See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing).  | @semantic-release-bot.               |
 | `GIT_COMMITTER_EMAIL` | The committer email associated with the [Git release tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging). See [Git environment variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_committing). | @semantic-release-bot email address. |

-## Existing version tags
+## Existing version tags, and how semantic-release deals with them

-**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 branches](#branches) 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.

@@ -0,0 +1,32 @@
+# Getting started
+
+## Manual setup
+
+You can use **semantic-release** with the following manual setup steps:
+
+1. [Install **semantic-release**](installation.md) either locally for your project or globally
+1. Configure:
+    1. Your Continuous Integration service to [run **semantic-release**](ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded)
+    1. Your Git repository and package manager repository [authentication](ci-configuration.md#authentication) in your Continuous Integration service
+    1. **semantic-release**'s [options and plugins](configuration.md)
+
+## Guided setup through `semantic-release-cli`
+Alternatively you can be guided through those setup steps thanks to the [interactive CLI `semantic-release-cli`](https://github.com/semantic-release/cli).
+
+First install `semantic-release-cli`:
+```bash
+$ npm install -g semantic-release-cli
+```
+
+Then go to your project's directory and run the command:
+```bash
+$ cd your-module
+$ semantic-release-cli setup
+```
+The output looks something like this:
+
+![dialogue](../../media/semantic-release-cli.png)
+
+Available options and other information can be found on [`semantic-release-cli`'s doc](https://github.com/semantic-release/cli#semantic-release-cli).
+
+> **Note**: only a limited number of options, CI services and plugins are currently supported by `semantic-release-cli`.
@@ -0,0 +1,22 @@
+# Installation
+
+## Local installation
+
+For [Node modules projects](https://docs.npmjs.com/getting-started/creating-node-modules) we recommend installing **semantic-release** locally and running the `semantic-release` command with [npx](https://www.npmjs.com/package/npx):
+
+```bash
+$ npm install --save-dev semantic-release
+```
+
+Then in the CI environment:
+
+```bash
+$ npx semantic-release
+```
+
+> **Note:** `npx` is a tool bundled with `npm@>=5.2.0`. It is used to conveniently find the semantic-release binary and to execute it. See [What is npx](../05-support/FAQ.md#what-is-npx) for more details.
+
+## Global installation
+
+> **Note:** For a global installation is no longer recommended. Please use local installation and `npx` instead.
+
@@ -1,13 +1,15 @@
 # Plugins

-Each [release step](../../README.md#release-steps) is implemented by configurable plugins. This allows for support of different [commit message formats](../../README.md#commit-message-format), release note generators and publishing platforms.
+## Plugins implement actions for release steps

-A plugin is a npm module that can implement one or more of the following steps:
+Actions that should be performed for each [release step](../../README.md#release-steps) are implemented through configurable plugins, and [a number of them are installed by default](#plugins-installed-by-default). This allows for support of different [commit message formats](../../README.md#commit-message-format), release note generators and publishing platforms.

-| Step               | Required | Description                                                                                                                                                                                                          |
+A plugin is a npm module (for instance `@semantic-release/github` or `semantic-release-docker`) that can implement one or more of the following steps through their step hooks:
+
+| Step hook          | Required | Description                                                                                                                                                                                                          |
 |--------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `verifyConditions` | No       | Responsible for verifying conditions necessary to proceed with the release: configuration is correct, authentication token are valid, etc...                                                                         |
-| `analyzeCommits`   | Yes      | Responsible for determining the type of the next release (`major`, `minor` or `patch`). If multiple plugins with a `analyzeCommits` step are defined, the release type will be the highest one among plugins output. |
+| `analyzeCommits`   | Yes      | Responsible for determining the type of the next release (`major`, `minor` or `patch`). If multiple plugins with a `analyzeCommits` step are defined, the release type will be the highest one among plugins output. <br> **Note**: If no plugin with an `analyzeCommits` step is defined, then `@semantic-release/commit-analyzer` will be used.|
 | `verifyRelease`    | No       | Responsible for verifying the parameters (version, type, dist-tag etc...) of the release that is about to be published.                                                                                              |
 | `generateNotes`    | No       | Responsible for generating the content of the release note. If multiple plugins with a `generateNotes` step are defined, the release notes will be the result of the concatenation of each plugin output.            |
 | `prepare`          | No       | Responsible for preparing the release, for example creating or updating files such as `package.json`, `CHANGELOG.md`, documentation or compiled assets and pushing a commit.                                         |
@@ -15,28 +17,32 @@ A plugin is a npm module that can implement one or more of the following steps:
 | `success`          | No       | Responsible for notifying of a new release.                                                                                                                                                                          |
 | `fail`             | No       | Responsible for notifying of a failed release.                                                                                                                                                                       |

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

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

-## Plugins configuration
+These five plugins are already part of **semantic-release** and don't have to be installed separately:
+```
+"@semantic-release/commit-analyzer"	
+"@semantic-release/error"	
+"@semantic-release/github"	
+"@semantic-release/npm"	
+"@semantic-release/release-notes-generator"
+```

-Each plugin must be installed and configured with the [`plugins` options](./configuration.md#plugins) by specifying the list of plugins by npm module name.
+### Installing additional plugins
+
+[Additional plugins](../02-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
 ```

-```json
-{
-  "plugins": ["@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/npm"]
-}
-```
+## Plugins declaration and execution order

-## Plugin ordering
-
-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.
+Each plugin (which is an npm module) must be declared using the [`plugins` option](./configuration.md#plugins). If the `plugins` option is defined, then the default is overriden (rather than merge with the option's default).

+For example:
 ```json
 {
  "plugins": [
@@ -48,16 +54,18 @@ For each [release step](../../README.md#release-steps) the plugins that implemen
 }
 ```

-With this configuration **semantic-release** will:
+For each [release step](../../README.md#release-steps) the plugins that implement that step will be executed **in the order in which they are declared**.
+
+Hence, with this configuration above, **semantic-release** will:
 - execute the `verifyConditions` implementation of `@semantic-release/npm` then `@semantic-release/git`
 - execute the `analyzeCommits` implementation of `@semantic-release/commit-analyzer`
 - execute the `prepare` implementation of `@semantic-release/npm` then `@semantic-release/git`
 - execute the `generateNotes` implementation of `@semantic-release/release-notes-generator`
 - execute the `publish` implementation of `@semantic-release/npm`

-## Plugin options
+## Plugins configuration options

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

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

@@ -0,0 +1,7 @@
+# Shareable configurations
+
+A shareable configuration is an npm package that exports a **semantic-release** configuration object. It allows for use of the same configuration across several projects.
+
+Shareable configurations to be use can be declared with the [`extends` option](configuration.md#extends).
+
+See [shareable configurations list](../02-extending/shareable-configurations-list.md) for examples.
@@ -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
@@ -41,6 +45,10 @@

 [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
@@ -71,3 +79,15 @@
  - `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.
@@ -0,0 +1,13 @@
+# Shareable configurations list
+
+## Official configurations
+- [@semantic-release/apm-config](https://github.com/semantic-release/apm-config) - semantic-release shareable configuration for releasing atom packages
+- [@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.
@@ -0,0 +1,3 @@
+# Git hosted services
+- [Git authentication with SSH keys](git-auth-ssh-keys.md)
+
@@ -0,0 +1,4 @@
+# CI pipelines recipes
+- [CircleCI 2.0 workflows](circleci-workflows.md)
+- [Travis CI](travis.md)
+- [GitLab CI](gitlab-ci.md)
@@ -2,9 +2,9 @@

 ## Environment variables

-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)..
+The [Authentication](../01-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/getting-started.md#getting-started).
+Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../01-usage/getting-started.md#guided-setup-through-semantic-release-cli).

 ## Multiple Node jobs configuration

@@ -12,7 +12,7 @@ Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with

 This example is a minimal configuration for **semantic-release** with a build running Node 6 and 8. See [CircleCI documentation](https://circleci.com/docs/2.0) for additional configuration options.

-This example create the workflows `test_node_4`, `test_node_6`, `test_node_8` and `release`. The release workflows will [run `semantic-release` only after the all the `test_node_*` are successful](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).
+This example create the workflows `test_node_4`, `test_node_6`, `test_node_8` and `release`. The release workflows will [run `semantic-release` only after the all the `test_node_*` are successful](../01-usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).

 ```yaml
 version: 2
@@ -54,7 +54,7 @@ workflows:

 ### `package.json` configuration for multiple Node jobs

-A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
+A `package.json` is required only for [local](../01-usage/installation.md#local-installation) **semantic-release** installation.

 ```json
 {
@@ -1,6 +1,6 @@
 # Git authentication with SSH keys

-When using [environment variables](../usage/ci-configuration.md#authentication) to set up the Git authentication, the remote Git repository will automatically be accessed via [https](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#_the_http_protocols), independently of the [`repositoryUrl`](../usage/configuration.md#repositoryurl) format configured in the **semantic-release** [Configuration](../usage/configuration.md#configuration) (the format will be automatically converted as needed).
+When using [environment variables](../01-usage/ci-configuration.md#authentication) to set up the Git authentication, the remote Git repository will automatically be accessed via [https](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#_the_http_protocols), independently of the [`repositoryUrl`](../01-usage/configuration.md#repositoryurl) format configured in the **semantic-release** [Configuration](../01-usage/configuration.md#configuration) (the format will be automatically converted as needed).

 Alternatively the Git repository can be accessed via [SSH](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols#_the_ssh_protocol) by creating SSH keys, adding the public one to your Git hosted account and making the private one available on the CI environment.

@@ -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
 ```
@@ -0,0 +1,2 @@
+# Git hosted services
+- [Git authentication with SSH keys](git-auth-ssh-keys.md)
@@ -2,19 +2,19 @@

 ## Environment variables

-The [Authentication](../usage/ci-configuration.md#authentication) environment variables can be configured with [Secret variables](https://docs.gitlab.com/ce/ci/variables/README.html#secret-variables).
+The [Authentication](../01-usage/ci-configuration.md#authentication) environment variables can be configured with [Secret variables](https://docs.gitlab.com/ce/ci/variables/README.html#secret-variables).

 ## Node project configuration

 GitLab CI supports [Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html) allowing to test on multiple Node versions and publishing a release only when all test pass.

-**Note**: The publish pipeline must run a [Node >= 8 version](../support/FAQ.md#why-does-semantic-release-require-node-version--83).
+**Note**: The publish pipeline must run a [Node >= 8 version](../05-support/FAQ.md#why-does-semantic-release-require-node-version--83).

 ### `.gitlab-ci.yml` configuration for Node projects

 This example is a minimal configuration for **semantic-release** with a build running Node 6 and 8. See [GitLab CI - Configuration of your jobs with .gitlab-ci.yml](https://docs.gitlab.com/ee/ci/yaml/README.html) for additional configuration options.

-**Note**: The`semantic-release` execution command varies depending if you are using a [local](../usage/installation.md#local-installation) or [global](../usage/installation.md#global-installation) **semantic-release** installation.
+**Note**: The`semantic-release` execution command varies depending if you are using a [local](../01-usage/installation.md#local-installation) or [global](../01-usage/installation.md#global-installation) **semantic-release** installation.

 ```yaml
 # The release pipeline will run only if all jobs in the test pipeline are successful
@@ -46,7 +46,7 @@ publish:

 ### `package.json` configuration

-A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
+A `package.json` is required only for [local](../01-usage/installation.md#local-installation) **semantic-release** installation.

 ```json
 {
@@ -0,0 +1,2 @@
+# Package managers and languages (to be completed)
+
@@ -2,9 +2,9 @@

 ## 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).
+The [Authentication](../01-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/getting-started.md#getting-started).
+Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with semantic-release-cli](../01-usage/01-getting-started.md#getting-started).

 ## Node.js projects configuration

@@ -12,7 +12,7 @@ Alternatively, the default `NPM_TOKEN` and `GH_TOKEN` can be easily [setup with

 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).
+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](../01-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.

@@ -43,7 +43,7 @@ jobs:

 ### `package.json` configuration for multiple Node jobs

-A `package.json` is required only for [local](../usage/installation.md#local-installation) **semantic-release** installation.
+A `package.json` is required only for [local](../01-usage/installation.md#local-installation) **semantic-release** installation.

 ```json
 {
@@ -57,13 +57,13 @@ A `package.json` is required only for [local](../usage/installation.md#local-ins

 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.
+This recipe cover the Travis specifics only. See [Non JavaScript projects recipe](../05-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).
+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](../01-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.

@@ -12,14 +12,7 @@ const stderrBuffer = WritableStreamBuffer();
 try {
  const result = await semanticRelease({
    // Core options
-    branches: [
-      '+([1-9])?(.{+([1-9]),x}).x',
-      'master',
-      'next',
-      'next-major',
-      {name: 'beta', prerelease: true},
-      {name: 'alpha', prerelease: true}
-    ],
+    branch: 'master',
    repositoryUrl: 'https://github.com/me/my-package.git',
    // Shareable config
    extends: 'my-shareable-config',
@@ -46,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.');
@@ -72,9 +65,9 @@ Type: `Object`

 **semantic-release** options.

-Can be used to set any [core option](../usage/configuration.md#configuration) or [plugin options](../usage/plugins.md#configuration).
+Can be used to set any [core option](../01-usage/configuration.md#configuration) or [plugin options](../01-usage/plugins.md#configuration).

-Each option, will take precedence over options configured in the [configuration file](../usage/configuration.md#configuration) and [shareable configurations](../usage/configuration.md#extends).
+Each option, will take precedence over options configured in the [configuration file](../01-usage/configuration.md#configuration) and [shareable configurations](../01-usage/configuration.md#extends).

 #### config

@@ -130,12 +123,11 @@ Type: `Object`

 Information related to the last release found:

-| Name    | Type     | Description                                                                                                                         |
-|---------|----------|-------------------------------------------------------------------------------------------------------------------------------------|
-| version | `String` | The version of the last release.                                                                                                    |
-| gitHead | `String` | The sha of the last commit being part of the last release.                                                                          |
-| gitTag  | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the last release.                                  |
-| channel | `String` | The distribution channel on which the last release was initially made available (`undefined` for the default distribution channel). |
+| Name    | Type     | Description                                                                                        |
+|---------|----------|----------------------------------------------------------------------------------------------------|
+| version | `String` | The version of the last release.                                                                   |
+| gitHead | `String` | The sha of the last commit being part of the last release.                                         |
+| gitTag  | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the last release. |

 **Notes**: If no previous release is found, `lastRelease` will be an empty `Object`.

@@ -145,7 +137,6 @@ Example:
  gitHead: 'da39a3ee5e6b4b0d3255bfef95601890afd80709',
  version: '1.0.0',
  gitTag: 'v1.0.0',
-  channel: 'next'
 }
 ```

@@ -215,14 +206,13 @@ Type: `Object`

 Information related to the newly published release:

-| Name    | Type     | Description                                                                                                                   |
-|---------|----------|-------------------------------------------------------------------------------------------------------------------------------|
-| type    | `String` | The [semver](https://semver.org) type of the release (`patch`, `minor` or `major`).                                           |
-| version | `String` | The version of the new release.                                                                                               |
-| gitHead | `String` | The sha of the last commit being part of the new release.                                                                     |
-| gitTag  | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the new release.                             |
-| notes   | `String` | The release notes for the new release.                                                                                        |
-| channel | `String` | The distribution channel on which the next release will be made available (`undefined` for the default distribution channel). |
+| Name    | Type     | Description                                                                                       |
+|---------|----------|---------------------------------------------------------------------------------------------------|
+| type    | `String` | The [semver](https://semver.org) type of the release (`patch`, `minor` or `major`).               |
+| version | `String` | The version of the new release.                                                                   |
+| gitHead | `String` | The sha of the last commit being part of the new release.                                         |
+| gitTag  | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the new release. |
+| notes   | `String` | The release notes for the new release.                                                            |

 Example:
 ```js
@@ -232,7 +222,6 @@ Example:
  version: '1.1.0',
  gitTag: 'v1.1.0',
  notes: 'Release notes for version 1.1.0...',
-  channel : 'next'
 }
 ```

@@ -240,20 +229,19 @@ Example:

 Type: `Array<Object>`

-The list of releases published or made available to a distribution channel.<br>
+The list of releases published, one release per [publish plugin](../01-usage/plugins.md#publish-plugin).<br>
 Each release object has the following properties:

-| Name       | Type     | Description                                                                                                    |
-|------------|----------|----------------------------------------------------------------------------------------------------------------|
-| name       | `String` | **Optional.** The release name, only if set by the corresponding `publish` plugin.                             |
-| url        | `String` | **Optional.** The release URL, only if set by the corresponding `publish` plugin.                              |
-| type       | `String` | The [semver](https://semver.org) type of the release (`patch`, `minor` or `major`).                            |
-| version    | `String` | The version of the release.                                                                                    |
-| gitHead    | `String` | The sha of the last commit being part of the release.                                                          |
-| gitTag     | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the release.                  |
-| notes      | `String` | The release notes for the release.                                                                             |
-| pluginName | `String` | The name of the plugin that published the release.                                                             |
-| channel    | `String` | The distribution channel on which the release is available (`undefined` for the default distribution channel). |
+| Name       | Type     | Description                                                                                   |
+|------------|----------|-----------------------------------------------------------------------------------------------|
+| name       | `String` | **Optional.** The release name, only if set by the corresponding `publish` plugin.            |
+| url        | `String` | **Optional.** The release URL, only if set by the corresponding `publish` plugin.             |
+| type       | `String` | The [semver](https://semver.org) type of the release (`patch`, `minor` or `major`).           |
+| version    | `String` | The version of the release.                                                                   |
+| gitHead    | `String` | The sha of the last commit being part of the release.                                         |
+| gitTag     | `String` | The [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) associated with the release. |
+| notes      | `String` | The release notes for the release.                                                            |
+| pluginName | `String` | The name of the plugin that published the release.                                            |

 Example:
 ```js
@@ -267,7 +255,6 @@ Example:
    gitTag: 'v1.1.0',
    notes: 'Release notes for version 1.1.0...',
    pluginName: '@semantic-release/github'
-    channel: 'next'
  },
  {
    name: 'npm package (@latest dist-tag)',
@@ -278,7 +265,6 @@ Example:
    gitTag: 'v1.1.0',
    notes: 'Release notes for version 1.1.0...',
    pluginName: '@semantic-release/npm'
-    channel: 'next'
   }
 ]
 ```
@@ -0,0 +1,106 @@
+# 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) {
+    //...
+}
+```
@@ -34,11 +34,11 @@ If using npm hook scripts is not possible, and alternative solution is to [`@sem

 ## Is there a way to preview which version would currently get published?

-Yes with the [dry-run options](../usage/configuration.md#dryrun) which prints to the console the next version to be published and the release notes.
+Yes with the [dry-run options](../01-usage/configuration.md#dryrun) which prints to the console the next version to be published and the release notes.

 ## Can I use semantic-release with Yarn?

-If you are using a [local](../usage/installation.md#local-installation) **semantic-release** installation and run multiple CI jobs with different versions, the `yarn install` command will fail on jobs running with Node < 8 as **semantic-release** requires [Node >= 8.3](#why-does-semantic-release-require-node-version--83) and specifies it in its `package.json`s [`engines`](https://docs.npmjs.com/files/package.json#engines) key.
+If you are using a [local](../01-usage/installation.md#local-installation) **semantic-release** installation and run multiple CI jobs with different versions, the `yarn install` command will fail on jobs running with Node < 8 as **semantic-release** requires [Node >= 8.3](#why-does-semantic-release-require-node-version--83) and specifies it in its `package.json`s [`engines`](https://docs.npmjs.com/files/package.json#engines) key.

 The recommended solution is to use the [Yarn](https://yarnpkg.com) [--ignore-engines](https://yarnpkg.com/en/docs/cli/install#toc-yarn-install-ignore-engines) option to install the project dependencies on the CI environment, so Yarn will ignore the **semantic-release**'s `engines` key:

@@ -48,7 +48,7 @@ $ yarn install --ignore-engines

 **Note**: Several CI services use Yarn by default if your repository contains a `yarn.lock` file. So you should override the install step to specify `yarn install --ignore-engines`.

-Alternatively you can use a [global](../usage/installation.md#global-installation) **semantic-release** installation and make sure to install and run the `semantic-release` command only in a CI jobs running with Node >= 8.3.
+Alternatively you can use a [global](../01-usage/installation.md#global-installation) **semantic-release** installation and make sure to install and run the `semantic-release` command only in a CI jobs running with Node >= 8.3.

 If your CI environment provides [nvm](https://github.com/creationix/nvm) you can switch to Node 8 before installing and running the `semantic-release` command:

@@ -56,14 +56,14 @@ If your CI environment provides [nvm](https://github.com/creationix/nvm) you can
 $ nvm install 8 && yarn global add semantic-release && semantic-release
 ```

-See the [CI configuration recipes](../recipes/README.md#ci-configurations) for more details on specific CI environments.
+See the [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details on specific CI environments.

 As `semantic-release` is recommended to be executed with [`npx`](https://www.npmjs.com/package/npx) an alternative is required for usage with Yarn. Even though it is possible to install npx with Yarn, it's not recommended. Yarn and npx would be using different cache locations.

-For [local installation](../usage/installation.md#local-installation) replace
+For [local installation](../01-usage/installation.md#local-installation) replace
 `npx semantic-release` with `yarn run semantic-release`.

-For [global installation](../usage/installation.md#global-installation) replace
+For [global installation](../01-usage/installation.md#global-installation) replace
 `npx semantic-release` with `yarn global add semantic-release && semantic-release`.

 ## Can I use semantic-release to publish non-JavaScript packages?
@@ -71,13 +71,13 @@ For [global installation](../usage/installation.md#global-installation) replace
 Yes, **semantic-release** is a Node CLI application but it can be used to publish any type of packages.

 To publish a non-Node package (without a `package.json`) you would need to:
- Use a [global](../usage/installation.md#global-installation) **semantic-release** installation
- Set **semantic-release** [options](../usage/configuration.md#options) via [CLI arguments or rc file](../usage/configuration.md#configuration)
+- Use a [global](../01-usage/installation.md#global-installation) **semantic-release** installation
+- Set **semantic-release** [options](../01-usage/configuration.md#options) via [CLI arguments or rc file](../01-usage/configuration.md#configuration)
 - Make sure your CI job executing the `semantic-release` command has access to [Node >= 8](#why-does-semantic-release-require-node-version--83) to execute the `semantic-release` command

-See the [CI configuration recipes](../recipes/README.md#ci-configurations) for more details on specific CI environments.
+See the [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details on specific CI environments.

-In addition you will need to configure the **semantic-release** [plugins](../usage/plugins.md#plugins) to disable the [`@semantic-release/npm`](https://github.com/semantic-release/npm) plugin which is used by default and use a plugin for your project type.
+In addition you will need to configure the **semantic-release** [plugins](../01-usage/plugins.md#plugins) to disable the [`@semantic-release/npm`](https://github.com/semantic-release/npm) plugin which is used by default and use a plugin for your project type.

 If there is no specific plugin for your project type you can use the [`@semantic-release/exec`](https://github.com/semantic-release/exec) plugin to publish the release with a shell command.

@@ -99,19 +99,19 @@ Here is a basic example to create [GitHub releases](https://help.github.com/arti

 **Note**: This is a theoretical example where the command `set-version` update the project version with the value passed as its first argument and `publish-package` publishes the package to a registry.

-See the [package managers and languages recipes](../recipes/README.md#package-managers-and-languages) for more details on specific project types.
+See the [package managers and languages recipes](../03-recipes/README.md#package-managers-and-languages) for more details on specific project types.

 ## Can I use semantic-release with any CI service?

 Yes, **semantic-release** can be used with any CI service, as long as it provides:
- A way to set [authentication](../usage/ci-configuration.md#authentication) via environment variables
- A way to guarantee that the `semantic-release` command is [executed only after all the tests of all the jobs in the CI build pass](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded)
+- A way to set [authentication](../01-usage/ci-configuration.md#authentication) via environment variables
+- A way to guarantee that the `semantic-release` command is [executed only after all the tests of all the jobs in the CI build pass](../01-usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded)

-See the [CI configuration recipes](../recipes/README.md#ci-configurations) for more details on specific CI environments.
+See the [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details on specific CI environments.

 ## Can I run semantic-release on my local machine rather than on a CI server?

-Yes, you can by explicitly setting the [`--no-ci` CLI option](../usage/configuration.md#ci) option. You will also have to set the required [authentication](../usage/ci-configuration.md#authentication) via environment variables on your local machine, for example:
+Yes, you can by explicitly setting the [`--no-ci` CLI option](../01-usage/configuration.md#ci) option. You will also have to set the required [authentication](../01-usage/ci-configuration.md#authentication) via environment variables on your local machine, for example:

 ```bash
 $ NPM_TOKEN=<your_npm_token> GH_TOKEN=<your_github_token> npx semantic-release --no-ci
@@ -123,11 +123,11 @@ However this is not the recommended approach, as running unit and integration te

 Yes, with the [`@semantic-release/gitlab-config`](https://github.com/semantic-release/gitlab-config) shareable configuration.

-See the [GitLab CI recipes](../recipes/gitlab-ci.md#using-semantic-release-with-gitlab-ci) for the CI configuration.
+See the [GitLab CI recipes](../03-recipes/gitlab-ci.md#using-semantic-release-with-gitlab-ci) for the CI configuration.

 ## Can I use semantic-release with any Git hosted environment?

-By default **semantic-release** uses the [`@semantic-release/github`](https://github.com/semantic-release/github) plugin to publish a [GitHub release](https://help.github.com/articles/about-releases). For other Git hosted environment the  [`@semantic-release/git`](https://github.com/semantic-release/git) and [`@semantic-release/changelog`](https://github.com/semantic-release/changelog) plugins can be used via [plugins configuration](../usage/plugins.md).
+By default **semantic-release** uses the [`@semantic-release/github`](https://github.com/semantic-release/github) plugin to publish a [GitHub release](https://help.github.com/articles/about-releases). For other Git hosted environment the  [`@semantic-release/git`](https://github.com/semantic-release/git) and [`@semantic-release/changelog`](https://github.com/semantic-release/changelog) plugins can be used via [plugins configuration](../01-usage/plugins.md).

 See the [`@semantic-release/git`](https://github.com/semantic-release/git#semantic-releasegit) [`@semantic-release/changelog`](https://github.com/semantic-release/changelog#semantic-releasechangelog) plugins documentation for more details.

@@ -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.

@@ -230,13 +230,13 @@ See [“Introduction to SemVer” - Irina Gebauer](https://blog.greenkeeper.io/i

 **semantic-release** has a full unit and integration test suite that tests `npm` publishes against the [npm-registry-couchapp](https://github.com/npm/npm-registry-couchapp).

-In addition the [verify conditions step](../../README.md#release-steps) verifies that all necessary conditions for proceeding with a release are met, and a new release will be performed [only if all your tests pass](../usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).
+In addition the [verify conditions step](../../README.md#release-steps) verifies that all necessary conditions for proceeding with a release are met, and a new release will be performed [only if all your tests pass](../01-usage/ci-configuration.md#run-semantic-release-only-after-all-tests-succeeded).

 ## Why does semantic-release require Node version >= 8.3?

 **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 @@ See our [Node Support Policy](node-support-policy.md) for our long-term promise

 The recommended approach is to run the `semantic-release` command from a CI job running on Node 8.3 or higher. This can either be a job used by your project to test on Node >= 8.3 or a dedicated job for the release steps.

-See [CI configuration](../usage/ci-configuration.md) and [CI configuration recipes](../recipes/README.md#ci-configurations) for more details.
+See [CI configuration](../01-usage/ci-configuration.md) and [CI pipelines recipes](../03-recipes/ci-pipelines-recipes.md) for more details.

 ## Alternative solutions

@@ -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
@@ -1,7 +1,7 @@
 # semantic-release documentation

- [Usage](usage/README.md) - **semantic-release** installation and configuration
- [Extending](extending/README.md)- Extending **semantic-release** with plugins and shareable configurations
- [Recipes](recipes/README.md) - Community written recipes for common **semantic-release** use-cases
- [Developer Guide](developer-guide/README.md) - The essentials of writing a **semantic-release** plugin or shareable configurations
- [Support](support/README.md) - FAQ and troubleshooting
+- [Usage](01-usage/README.md) - **semantic-release** installation and configuration
+- [Extending](02-extending/README.md)- Extending **semantic-release** with plugins and shareable configurations
+- [Recipes](03-recipes/README.md) - Community written recipes for common **semantic-release** use-cases
+- [Developer Guide](04-developer-guide/README.md) - The essentials of writing a **semantic-release** plugin or shareable configurations
+- [Support](05-support/README.md) - FAQ and troubleshooting
@@ -1 +0,0 @@
-# Plugin developer guide
@@ -1,7 +0,0 @@
-# Shareable configurations list
-
-## Official configurations
- [@semantic-release/apm-config](https://github.com/semantic-release/apm-config) - semantic-release shareable configuration for releasing atom packages
- [@semantic-release/gitlab-config](https://github.com/semantic-release/gitlab-config) - semantic-release shareable configuration for GitLab
-
-## Community configurations
@@ -1,16 +0,0 @@
-# Recipes
-
-## CI configurations
- [CircleCI 2.0 workflows](circleci-workflows.md)
- [Travis CI](travis.md)
- [GitLab CI](gitlab-ci.md)
-
-## Git hosted services
- [Git authentication with SSH keys](git-auth-ssh-keys.md)
-
-## Release workflow
- [Publishing on distribution channels](distribution-channels.md)
- [Publishing maintenance releases](maintenance-releases.md)
- [Publishing pre-releases](pre-releases.md)
-
-## Package managers and languages
@@ -1,116 +0,0 @@
-# Publishing on distribution channels
-
-This recipe will walk you through a simple example that uses distribution channels to make releases available only to a subset of users, in order to collect feedbacks before distributing the release to all users.
-
-This example uses the **semantic-release** default configuration:
- [branches](../usage/configuration.md#branches): `['+([1-9])?(.{+([1-9]),x}).x', 'master', 'next', 'next-major', {name: 'beta', prerelease: true}, {name: 'alpha', prerelease: true}]`
- [plugins](../usage/configuration.md#plugins): `['@semantic-release/commit-analyzer', '@semantic-release/release-notes-generator', '@semantic-release/npm', '@semantic-release/github']`
-
-## Initial release
-
-We'll start by making the first commit of the project, with the code for the initial release and the message `feat: initial commit` to `master`. When pushing that commit, **semantic-release** will release the version `1.0.0` and make it available on the default distribution channel which is the dist-tag `@latest` for npm.
-
-The Git history of the repository is:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-```
-
-## Releasing a bug fix
-
-We can now continue to commit changes and release updates to our users. For example we can commit a bug fix with the message `fix: a fix` to `master`. When pushing that commit, **semantic-release** will release the version `1.0.1` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-```
-
-## Releasing a feature on next
-
-We now want to develop an important feature, which is a breaking change. Considering the scope of this feature we want to make it available, at first, only to our most dedicated users in order to get feedback. Once we get that feedback we can make improvements and ultimately make the new feature available to all users.
-
-To implement that workflow we can create the branch `next` and commit our feature to this branch. When pushing that commit, **semantic-release** will release the version `2.0.0` on the dist-tag `@next`. That means only the users installing our module with `npm install example-module@next` will receive the version `2.0.0`. Other users installing with `npm install example-module` will still receive the version `1.0.1`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-| \
-|  * feat: a big feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0 on @next
-```
-
-## Releasing a bug fix on next
-
-One of our users starts to use the new `2.0.0` release and reports a bug. We develop a bug fix and commit it to the `next` branch with the message `fix: fix something on the big feature`. When pushing that commit, **semantic-release** will release the version `2.0.1` on the dist-tag `@next`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-| \
-|  * feat: a big feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0 on @next
-|  * fix: fix something on the big feature # => v2.0.1 on @next
-```
-
-## Releasing a feature on latest
-
-We now want to develop a smaller, non-breaking feature. Its scope is small enough that we don't need to have a phase of feedback and we can release it to all users right away.
-
-If we were to commit that feature on `next` only a subset of users would get it, and we would need to wait for the end of our feedback period in order to make both the big and the small feature available to all users.
-
-Instead, we develop that small feature commit it to `master` with the message `feat: a small feature`. When pushing that commit, **semantic-release** will release the version `1.1.0` on the dist-tag `@latest` so all users can benefit from it right away.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-| \
-|  * feat: a big feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0 on @next
-|  * fix: fix something on the big feature # => v2.0.1 on @next
-*  | feat: a small feature # => v1.1.0 on @latest
-```
-
-## Porting a feature to next
-
-Most of our users now have access to the small feature, but we still need to make it available to our users using the `@next` dist-tag. To do so we need to merge our changes made on `master` (the commit `feat: a small feature`) into `next`. As `master` and `next` branches have diverged, this merge might require to resolve conflicts.
-
-Once the conflicts are resolved and the merge commit is pushed to `next`, **semantic-release** will release the version `2.1.0` on the dist-tag `@next` which contains both our small and big feature.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-| \
-|  * feat: a big feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0 on @next
-|  * fix: fix something on the big feature # => v2.0.1 on @next
-*  | feat: a small feature # => v1.1.0 on @latest
-|  * Merge branch master into next # => v2.1.0 on @next
-```
-
-## Adding a version to latest
-
-After a period of feedback from our users using the `@next` dist-tag we feel confident to make our big feature available to all users. To do so we merge the `next` branch into `master`. There should be no conflict as `next` is strictly ahead of `master`.
-
-Once the merge commit is pushed to `next`, **semantic-release** will add the version `2.1.0` to the dist-tag `@latest` so all users will receive it when installing out module with `npm install example-module`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* fix: a fix # => v1.0.1 on @latest
-| \
-|  * feat: a big feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0 on @next
-|  * fix: fix something on the big feature # => v2.0.1 on @next
-*  | feat: a small feature # => v1.1.0 on @latest
-|  * Merge branch master into next # => v2.1.0 on @next
-| /|
-*  | Merge branch next into master # => v2.1.0 on @latest
-```
-
-We can now continue to push new fixes and features on `master`, or a new breaking change on `next` as we did before.
@@ -1,156 +0,0 @@
-# Publishing maintenance releases
-
-This recipe will walk you through a simple example that uses Git branches and distribution channels to publish fixes and features for old versions of a package.
-
-This example uses the **semantic-release** default configuration:
- [branches](../usage/configuration.md#branches): `['+([1-9])?(.{+([1-9]),x}).x', 'master', 'next', 'next-major', {name: 'beta', prerelease: true}, {name: 'alpha', prerelease: true}]`
- [plugins](../usage/configuration.md#plugins): `['@semantic-release/commit-analyzer', '@semantic-release/release-notes-generator', '@semantic-release/npm', '@semantic-release/github']`
-
-## Initial release
-
-We'll start by making the first commit of the project, with the code for the initial release and the message `feat: initial commit`. When pushing that commit, on `master` **semantic-release** will release the version `1.0.0` and make it available on the default distribution channel which is the dist-tag `@latest` for npm.
-
-The Git history of the repository is:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-```
-
-## Releasing a breaking change
-
-We now decide to drop Node.js 6 support for our package, and require Node.js 8 or higher, which is a breaking change.  
-
-We commit that change with the message `feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required` to `master`. When pushing that commit, **semantic-release** will release the version `2.0.0` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-* feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-```
-
-## Releasing a feature for version 1.x users
-
-One of our users request a new feature, however they cannot migrate to Node.js 8 or higher due to corporate policies.
-
-If we were to push that feature on `master` and release it, the new version would require Node.js 8 or higher as the release would also contains the commit `feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required`.
-
-Instead, we create the branch `1.x` from the tag `v1.0.0` with the command `git checkout -b 1.x v1.0.0` and we commit that feature with the message `feat: a feature` to the branch `1.x`. When pushing that commit, **semantic-release** will release the version `1.1.0` on the dist-tag `@release-1.x` so users who can't migrate to Node.js 8 or higher can benefit from it.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  * feat: a feature # => v1.1.0 on @1.x
-```
-
-## Releasing a bug fix for version 1.0.x users
-
-Another user currently using version `1.0.0` reports a bug. They cannot migrate to Node.js 8 or higher and they also cannot migrate to `1.1.0` as they do not use the feature developed in `feat: a feature` and their corporate policies require to go through a costly quality insurance process for each `minor` upgrades.
-
-In order to deliver the bug fix in a `patch` release, we create the branch `1.0.x` from the tag `v1.0.0` with the command `git checkout -b 1.0.x v1.0.0` and we commit that fix with the message `fix: a fix` to the branch `1.0.x`. When pushing that commit, **semantic-release** will release the version `1.0.1` on the dist-tag `@release-1.0.x` so users who can't migrate to `1.1.x` or `2.x` can benefit from it.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  | \
-|  *  | feat: a feature # => v1.1.0 on @1.x
-|  |  * fix: a fix # => v1.0.1 on @1.0.x
-```
-
-## Porting a bug fix from 1.0.x to 1.x
-
-Now that we have released a fix in version `1.0.1` we want to make it available to `1.1.x` users as well.
-
-To do so we need to merge the changes made on `1.0.x` (the commit `fix: a fix`) into the `1.x` branch. As `1.0.x` and `1.x` branches have diverged, this merge might require to resolve conflicts.
-
-Once the conflicts are resolved and the merge commit is pushed to the branch `1.x`, **semantic-release** will release the version `1.1.1` on the dist-tag `@release-1.x` which contains both our feature and bug fix.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  | \
-|  *  | feat: a feature # => v1.1.0 on @1.x
-|  |  * fix: a fix # => v1.0.1 on @1.0.x
-|  | /|
-|  *  | Merge branch 1.0.x into 1.x # => v1.1.1 on @1.x
-```
-
-## Porting bug fixes and features to master
-
-Finally we want to make both our feature and bug fix available to users using the `@latest` dist-tag.
-
-To do so we need to merge the changes made on `1.x` (the commits `feat: a feature` and `fix: a fix`) into `master`. As `1.x` and `master` branches have diverged, this merge might require to resolve conflicts.
-
-Once the conflicts are resolved and the merge commit is pushed to `master`, **semantic-release** will release the version `2.1.0` on the dist-tag `@latest` which now contains the breaking change feature, the feature and the bug fix.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  | \
-|  *  | feat: a feature # => v1.1.0 on @1.x
-|  |  * fix: a fix # => v1.0.1 on @1.0.x
-|  | /|
-|  *  | Merge branch 1.0.x into 1.x # => v1.1.1 on @1.x
-| /|  |
-*  |  | Merge branch 1.x into master # => v2.1.0 on @latest
-```
-
-## Releasing a bug fix for version 2.1.0 users
-
-One of our users using the version `2.1.0` version reports a bug.
-
-We can simply commit the bug fix with the message `fix: another fix` to `master`. When pushing that commit, **semantic-release** will release the version `2.1.1` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  | \
-|  *  | feat: a feature # => v1.1.0 on @1.x
-|  |  * fix: a fix # => v1.0.1 on @1.0.x
-|  | /|
-|  *  | Merge branch 1.0.x into 1.x # => v1.1.1 on @1.x
-| /|  |
-*  |  | Merge branch 1.x into master # => v2.1.0 on @latest
-*  |  | fix: another fix # => v2.1.1 on @latest
-```
-
-## Porting a bug fix from master to 1.x
-
-The bug fix `fix: another fix` also affects version `1.1.1` users, so we want to port it to the `1.x` branch.
-
-To do so we need to cherry pick our fix commit made on `master` (`fix: another fix`) into `1.x` with `git checkout 1.x && git cherry-pick <sha of fix: another fix>`. As `master` and `1.x` branches have diverged, the cherry picking might require to resolve conflicts.
-
-Once the conflicts are resolved and the commit is pushed to `1.x`, **semantic-release** will release the version `1.1.2` on the dist-tag `@release-1.x` which contains `feat: a feature`, `fix: a fix` and `fix: another fix` but not `feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-*  | feat: drop Node.js 6 support \n\n BREAKING CHANGE: Node.js >= 8 required # => v2.0.0 on @latest
-|  | \
-|  *  | feat: a feature # => v1.1.0 on @1.x
-|  |  * fix: a fix # => v1.0.1 on @1.0.x
-|  | /|
-|  *  | Merge branch 1.0.x into 1.x # => v1.1.1 on @1.x
-| /|  |
-*  |  | Merge branch 1.x into master # => v2.1.0 on @latest
-*  |  | fix: another fix # => v2.1.1 on @latest
-|  |  |
-|  *  | fix: another fix # => v1.1.2 on @1.x
-```
@@ -1,196 +0,0 @@
-# Publishing pre-releases
-
-This recipe will walk you through a simple example that uses pre-releases to publish beta versions while working on a future major release and then make only one release on the default distribution.
-
-This example uses the **semantic-release** default configuration:
- [branches](../usage/configuration.md#branches): `['+([1-9])?(.{+([1-9]),x}).x', 'master', 'next', 'next-major', {name: 'beta', prerelease: true}, {name: 'alpha', prerelease: true}]`
- [plugins](../usage/configuration.md#plugins): `['@semantic-release/commit-analyzer', '@semantic-release/release-notes-generator', '@semantic-release/npm', '@semantic-release/github']`
-
-## Initial release
-
-We'll start by making the first commit of the project, with the code for the initial release and the message `feat: initial commit`. When pushing that commit, on `master` **semantic-release** will release the version `1.0.0` and make it available on the default distribution channel which is the dist-tag `@latest` for npm.
-
-The Git history of the repository is:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-```
-
-## Working on a future release
-
-We now decide to work on a future major release, which will be composed of multiple features, some of them being breaking changes. We want to publish our package for each new feature developed for test purpose, however we do not want to increment our package version or make it available to our users until all the features are developed and tested.
-
-To implement that workflow we can create the branch `beta` and commit our first feature there. When pushing that commit, **semantic-release** will publish the pre-release version `2.0.0-beta.1` on the dist-tag `@beta`. That allow us to run integration tests by installing our module with `npm install example-module@beta`. Other users installing with `npm install example-module` will still receive the version `1.0.0`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-```
-
-We can continue to work on our future release by committing and pushing other features or bug fixes on the `beta` branch. With each push, **semantic-release** will publish a new pre-release on the dist-tag `@beta`, which allow us to run our integration tests.
-
-With another feature, the Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-```
-
-## Releasing a bug fix on the default distribution channel
-
-In the meantime we can also continue to commit changes and release updates to our users.
-
-For example, we can commit a bug fix with the message `fix: a fix` to `master`. When pushing that commit, **semantic-release** will release the version `1.0.1` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-```
-
-## Working on another future release
-
-We now decide to work on another future major release, in parallel of the beta one, which will also be composed of multiple features, some of them being breaking changes.
-
-To implement that workflow we can create the branch `alpha` from the branch `beta` and commit our first feature there. When pushing that commit, **semantic-release** will publish the pre-release version `3.0.0-alpha.1` on the dist-tag `@alpha`. That allow us to run integration tests by installing our module with `npm install example-module@alpha`. Other users installing with `npm install example-module` will still receive the version `1.0.0`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-```
-
-We can continue to work on our future release by committing and pushing other features or bug fixes on the `alpha` branch. With each push, **semantic-release** will publish a new pre-release on the dist-tag `@alpha`, which allow us to run our integration tests.
-
-With another feature, the Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-|  |  * feat: second feature of other release # => v3.0.0-alpha.2 on @alpha
-```
-
-## Publishing the 2.0.0 beta release to the default distribution channel
-
-Once we've developed and pushed all the feature we want to include in the future version `2.0.0` in the `beta` branch and all our tests are successful we can release it to our users.
-
-To do so we need to merge our changes made on `beta` into `master`. As `beta` and `master` branches have diverged, this merge might require to resolve conflicts.
-
-Once the conflicts are resolved and the merge commit is pushed to `master`, **semantic-release** will release the version `2.0.0` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-|  |  * feat: second feature of other release # => v3.0.0-alpha.2 on @alpha
-| /|  |
-*  |  | Merge branch beta into master # => v2.0.0 on @latest
-```
-
-## Publishing the 3.0.0 alpha release to the beta distribution channel
-
-Now that we published our the version `2.0.0` that was previously in beta, we decide to promote the version `3.0.0` in alpha to beta.
-
-To do so we need to merge our changes made on `alpha` into `beta`. There should be no conflict as `alpha` is strictly ahead of `master`.
-
-Once the merge commit is pushed to `beta`, **semantic-release** will publish the pre-release version `3.0.0-beta.1` on the dist-tag `@beta`, which allow us to run our integration tests.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-|  |  * feat: second feature of other release # => v3.0.0-alpha.2 on @alpha
-| /|  |
-*  |  | Merge branch beta into master # => v2.0.0 on @latest
-|  | /|
-|  *  | Merge branch alpha into beta # => v3.0.0-beta.1 on @beta
-```
-
-## Publishing the 3.0.0 beta release to the default distribution channel
-
-Once we've developed and pushed all the feature we want to include in the future version `3.0.0` in the `beta` branch and all our tests are successful we can release it to our users.
-
-To do so we need to merge our changes made on `beta` into `master`. As `beta` and `master` branches have diverged, this merge might require to resolve conflicts.
-
-Once the conflicts are resolved and the merge commit is pushed to `master`, **semantic-release** will release the version `3.0.0` on the dist-tag `@latest`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-|  |  * feat: second feature of other release # => v3.0.0-alpha.2 on @alpha
-| /|  |
-*  |  | Merge branch beta into master # => v2.0.0 on @latest
-|  | /|
-|  *  | Merge branch alpha into beta # => v3.0.0-beta.1 on @beta
-| /|  |
-*  |  | Merge branch beta into master # => v3.0.0 on @latest
-```
-
-## Working on a third future release
-
-We can now start to work on a new future major release, version `4.0.0`, on the `@beta` distribution channel.
-
-To do so we fist need to update the `beta` branch with all the changes from `master` (the commits `fix: a fix`). As `beta` and `master` branches have diverged, this merge might require to resolve conflicts.
-
-We can now commit our new feature on `beta`. When pushing that commit, **semantic-release** will publish the pre-release version `3.1.0-beta.1` on the dist-tag `@beta`. That allow us to run integration tests by installing our module with `npm install example-module@beta`. Other users installing with `npm install example-module` will still receive the version `3.0.0`.
-
-The Git history of the repository is now:
-
-```
-* feat: initial commit # => v1.0.0 on @latest
-| \
-|  * feat: first feature \n\n BREAKING CHANGE: it breaks something # => v2.0.0-beta.1 on @beta
-|  * feat: second feature # => v2.0.0-beta.2 on @beta
-*  | fix: a fix # => v1.0.1 on @latest
-|  | \
-|  |  * feat: first feature of other release \n\n BREAKING CHANGE: it breaks something # => v3.0.0-alpha.1 on @alpha
-|  |  * feat: second feature of other release # => v3.0.0-alpha.2 on @alpha
-| /|  |
-*  |  | Merge branch beta into master # => v2.0.0 on @latest
-|  | /|
-|  *  | Merge branch alpha into beta # => v3.0.0-beta.1 on @beta
-| /|  |
-*  |  | Merge branch beta into master # => v3.0.0 on @latest
-| \|  |
-|  *  | Merge branch master into beta
-|  *  | feat: new feature # => v3.1.0-beta.1 on @beta
-```
@@ -1,22 +0,0 @@
-# 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)
-
-Alternatively those steps can be easily done with the [**semantic-release** interactive CLI](https://github.com/semantic-release/cli):
-
-```bash
-npm install -g semantic-release-cli
-
-cd your-module
-semantic-release-cli setup
-```
-
-![dialogue](../../media/semantic-release-cli.png)
-
-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`.
@@ -1,29 +0,0 @@
-# Installation
-
-## Local installation
-
-For [Node modules projects](https://docs.npmjs.com/getting-started/creating-node-modules) we recommend installing **semantic-release** locally and running the `semantic-release` command with [npx](https://www.npmjs.com/package/npx):
-
-```bash
-$ npm install --save-dev semantic-release
-```
-
-Then in the CI environment:
-
-```bash
-$ npx semantic-release
-```
-
-**Note:** `npx` is a tool bundled with `npm@>=5.2.0`. It is used to conveniently find the semantic-release binary and to execute it. See [What is npx](../support/FAQ.md#what-is-npx) for more details.
-
-## Global installation
-
-For other type of projects we recommend installing **semantic-release** directly in the CI environment, also with [npx](https://www.npmjs.com/package/npx):
-
-```bash
-$ 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:** `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.
@@ -1,7 +0,0 @@
-# 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.
-
-The shareable configurations to use can be set with the [extends](configuration.md#extends) option.
-
-See [shareable configurations list](../extending/shareable-configurations-list.md).
@@ -1,187 +0,0 @@
-# Workflow configuration
-
-**semantic-release** allow to manage and automate complex release workflow, based on multiple Git branches and distribution channels. This allow to:
- Distributes certain releases to a particular group of users via distribution channels
- Manage the availability of releases on distribution channels via branches merge
- Maintain multiple lines of releases in parallel
- Work on large future releases outside the normal flow of one version increment per Git push
-
-See [Release workflow recipes](../recipes/README.md#release-workflow) for detailed examples.
-
-The release workflow is configured via the [branches option](./configuration.md#branches) which accepts a single or an array of branch definitions.
-Each branch can be defined either as a string, a [glob](https://github.com/micromatch/micromatch#matching-features) or an object. For string and glob definitions each [property](#branches-properties) will be defaulted.
-
-A branch can defined as one of three types:
- [release](#release-branches): to make releases on top of the last version released
- [maintenance](#maintenance-branches): to make release on top of an old release
- [pre-release](#pre-release-branches): to make pre-releases
-
-The type of the branch is automatically determined based on naming convention and/or [properties](#branches-properties).
-
-## Branches properties
-
-| Property     | Branch type                               | Description                                                                                                                                                                           | Default                                                                                         |
-|--------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|
-| `name`       | All                                       | **Required.** The Git branch holding the commits to analyze and the code to release. See [name](#name).                                                                               | - The value itself if defined as a `String` or the matching branches name if defined as a glob. |
-| `channel`    | All                                       | The distribution channel on which to publish releases from this branch. See [channel](#channel).                                                                                      | `undefined` for the first release branch, the value of `name` for subsequent ones.              |
-| `range`      | [maintenance](#maintenance-branches) only | **Required unless `name` is formatted like `N.N.x` or `N.x` (`N` is a number).** The range of [semantic versions](https://semver.org) to support on this branch. See [range](#range). | The value of `name`.                                                                            |
-| `prerelease` | [pre-release](#pre-release-branches) only | **Required.** The pre-release detonation to append to [semantic versions](https://semver.org) released from this branch. See [prerelease](#prerelease).                               | -                                                                                               |
-
-### name
-
-A `name` is required for any type of branch.
-It can be defined as a [glob](https://github.com/micromatch/micromatch#matching-features) in which case the definition will be expanded to one per matching branch existing in the repository.
-
-If `name` doesn't match to any branch existing in the repository, the definition will be ignored. For example the default configuration includes the definition `next` and `next-major` which will become active only when the branches `next` and/or `next-major` are created in the repository. This allow to define your workflow once with all potential branches you might use and have the effective configuration evolving as you create new branches.
-
-For example the configuration `['+([1-9])?(.{+([1-9]),x}).x', 'master', 'next']` will be expanded as:
-```js
-{
-  branches: [
-    {name: '1.x', range: '1.x', channel: '1.x'}, // Only after the `1.x` is created in the repo
-    {name: '2.x', range: '2.x', channel: '2.x'}, // Only after the `2.x` is created in the repo
-    {name: 'master'},
-    {name: 'next', channel: 'next'}, // Only after the `next` is created in the repo
-  ]
-}
-```
-
-### channel
-
-The `channel` can be defined for any branch type. If it's not defined, releases will be done on the default distribution channel (for example the `@latest` [dist-tag](https://docs.npmjs.com/cli/dist-tag) for npm).
-The value of `channel`, if defined, is generated with [Lodash template](https://lodash.com/docs#template) with the variable `name` available.
-
-For example the configuration `['master', {name: 'next', channel: 'channel-${name}'}]` will be expanded as:
-```js
-{
-  branches: [
-    {name: 'master'}, // `channel` is undefined so the default distribution channel will be used
-    {name: 'next', channel: 'channel-next'}, // `channel` is built with the template `channel-${name}`
-  ]
-}
-```
-
-### range
-
-A `range` only applies to maintenance branches, is required and must be formatted like `N.N.x` or `N.x` (`N` is a number). In case the `name` is formatted as a range (for example `1.x` or `1.5.x`) the branch will be considered a maintenance branch and the `name` value will be used for the `range`.
-
-For example the configuration `['1.1.x', '1.2.x', 'master']` will be expanded as:
-```js
-{
-  branches: [
-    {name: '1.1.x', range: '1.1.x', channel: '1.1.x'},
-    {name: '1.2.x', range: '1.2.x', channel: '1.2.x'},
-    {name: 'master'},
-  ]
-}
-```
-
-### prerelease
-
-A `prerelease` property applies only to pre-release branches, is required and The `prerelease` value must be valid per the [Semantic Versioning Specification](https://semver.org/#spec-item-9). It will determine the name of versions (for example if `prerelease` is set to `beta` the version be formatted like `2.0.0-beta.1`, `2.0.0-beta.2` etc...).
-If the `prerelease` property is set to `true` the `name` value will be used.
-
-The value of `prerelease`, if defined as a string, is generated with [Lodash template](https://lodash.com/docs#template) with the variable `name` available.
-
-For example the configuration `['master', {name: 'pre/rc', prerelease: '${name.replace(/^pre\\//g, "")}'}, {name: 'beta', prerelease: true}]` will be expanded as:
-```js
-{
-  branches: [
-    {name: 'master'},
-    {name: 'pre/rc', channel: 'pre/rc', prerelease: 'rc'}, // `prerelease` is built with the template `${name.replace(/^pre\\//g, "")}`
-    {name: 'beta', channel: 'beta', prerelease: 'beta'}, // `prerelease` is set to `beta` as it is the value of `name`
-  ]
-}
-```
-
-## Branch types
-
-### Release branches
-
-A release branch is the base type of branch used by **semantic-release** that allows to publish releases with a [semantic version](https://semver.org), optionally on a specific distribution channel. Distribution channels (for example [npm dist-tags](https://docs.npmjs.com/cli/dist-tag) or [Chrome release channels](https://www.chromium.org/getting-involved/dev-channel)) are a way to distribute new releases only to a subset of users in order to get early feedback. Later on those releases can be added to the general distribution channel to be made available to all users.
-
-**semantic-release** will automatically add releases to the corresponding distribution channel when code is [merged from a release branch to another](#merging-into-a-release-branch).
-
-A project must define a minimum of 1 release branch and can have a maximum of 3. The order of the release branch definitions is significant, as versions released on a given branch must always be higher than the last release made on the previous branch. This allow to avoid situation that would lead to an attempt to publish releases with the same version number but different codebase. When multiple release branches are configured and a commit that would create a version conflict is pushed, **semantic-release** will not perform the release and will throw an `EINVALIDNEXTVERSION` error, listing the problematic commits and the valid branches on which to move them.
-
-**Note:** With **semantic-release** as with most package managers, a release version must be unique, independently of the distribution channel on which it is available.
-
-See [publishing on distribution channels recipe](../recipes/distribution-channels.md) for a detailed example.
-
-#### Pushing to a release branch
-
-With the configuration `"branches": ["master", "next"]`, if the last release published from `master` is `1.0.0` then:
- Only versions in range `1.x.x` can be published from `master`, so only `fix` and `feat` commits can be pushed to `master`
- Only versions in range `>=2.0.0` release can be published from `next`, so a `BREAKING CHANGE` commit must be pushed first on `next` and can be followed by any type of commits
-
-With the configuration `"branches": ["master", "next", "next-major"]`, if the last release published from `master` is `1.0.0` then:
- Only versions in range `1.0.x` can be published from `master`, so only `fix` commits can be pushed to `master`
- Only versions in range `>=1.1.0` can be published from `next`, so a `feat` commit must be pushed first on `next` and can be followed by `fix` and `feat` commits
- Only versions in range `>=2.0.0` release can be published from `next`, so a `BREAKING CHANGE` commit must be pushed first on `next-major` and can be followed by any type of commits
-
-Those verifications prevent situations such as:
-1. Create a `feat` commit on `next` which triggers the release of version `1.0.0` on channel `next`
-2. Merge `next` into `master` which adds `1.0.0` on the default channel
-3. Push a `fix` commit to `master` which triggers the release of version `1.0.1` on the default channel
-4. Push a `fix` commit to `next` which would attempt to release the version `1.0.1` on channel `next` and fails as this version already exists
-
-#### Merging into a release branch
-
-When merging commits associated with a release from one release branch to another, **semantic-release** will make the corresponding version available on the channel associated with the target branch.
-
-When merging commits not associated with a release, commits from a [maintenance branch](#maintenance-branches) or commits from a [pre-release branch](#pre-release-branches) **semantic-release** will treat them as [pushed commits](#pushing-to-a-release-branch) and publish a new release if necessary.
-
-### Maintenance branches
-
-A maintenance branch is a type of branch used by **semantic-release** that allows to publish releases with a [semantic version](https://semver.org) on top of the codebase of an old release. This is useful when you need to provide fixes or features to users who cannot upgrade to the last version of your package.
-
-A maintenance branch is characterized by a range which defines the versions that can be published from it. The [`range`](#range) value of each maintenance branch must be unique across the project.
-
-**semantic-release** will always publish releases to a distribution channel specific to the range, so only the users who choose to use that particular line of versions will receive new releases.
-
-Maintenance branches are always considered lower than [release branches](#release-branches) and similarly to them, when a commit that would create a version conflict is pushed, **semantic-release** will not perform the release and will throw an `EINVALIDNEXTVERSION` error, listing the problematic commits and the valid branches on which to move them.
-
-**semantic-release** will automatically add releases to the corresponding distribution channel when code is [merged from a release or maintenance branch to another maintenance branch](#merging-into-a-maintenance-branch), however only version version within the branch `range` can be merged. Ia merged version is outside the maintenance branch `range` **semantic-release** will not add to the corresponding channel and will throw an `EINVALIDMAINTENANCEMERGE` error.
-
-See [publishing maintenance releases recipe](../recipes/maintenance-releases.md) for a detailed example.
-
-#### Pushing to a maintenance branch
-
-With the configuration `"branches": ["1.0.x", "1.x", "master"]`, if the last release published from `master` is `1.5.0` then:
- Only versions in range `>=1.0.0 <1.1.0` can be published from `1.0.x`, so only `fix` commits can be pushed to `1.0.x`
- Only versions in range `>=1.1.0 <1.5.0` can be published from `1.x`, so only `fix` and `feat` commits can be pushed to `1.x` as long the resulting release is lower than `1.5.0`
- Once `2.0.0` is released from `master`, versions in range `>=1.1.0 <2.0.0` can be published from `1.x`, so any number of `fix` and `feat` commits can be pushed to `1.x`
-
-#### Merging into a maintenance branch
-
-With the configuration `"branches": ["1.0.x", "1.x", "master"]`, if the last release published from `master` is `1.0.0` then:
- Creating the branch `1.0.x` from `master` will make the `1.0.0` release available on the `1.0.x` distribution channel
- Pushing a `fix` commit on the `1.0.x` branch will release the version `1.0.1` on the `1.0.x` distribution channel
- Creating the branch `1.x` from `master` will make the `1.0.0` release available on the `1.x` distribution channel
- Merging the branch `1.0.x` into `1.x` will make the version `1.0.1` available on the `1.x` distribution channel
-
-### Pre-release branches
-
-A pre-release branch is a type of branch used by **semantic-release** that allows to publish releases with a [pre-release version](https://semver.org/#spec-item-9).
-Using a pre-release version allow to publish multiple releases with the same version. Those release will be differentiated via there identifiers (in `1.0.0-alpha.1` the identifier is `alpha.1`).
-This is useful when you need to work on a future major release that will include many breaking changes but you do not want to increment the version number for each breaking change commit.
-
-A pre-release branch is characterized by the `prerelease` property that defines the static part of the version released (in `1.0.0-alpha.1` the static part fo the identifier is `alpha`). The [`prerelease`](#prerelease) value of each pre-release branch must be unique across the project.
-
-**semantic-release** will always publish pre-releases to a specific distribution channel, so only the users who choose to use that particular line of versions will receive new releases.
-
-When merging commits associated with an existing release, **semantic-release** will treat them as [pushed commits](#pushing-to-a-pre-release-branch) and publish a new release if necessary, but it will never add those releases to the distribution channel corresponding to the pre-release branch.
-
-See [publishing pre-releases recipe](../recipes/pre-releases.md) for a detailed example.
-
-#### Pushing to a pre-release branch
-
-With the configuration `"branches": ["master", {"name": "beta", "prerelease": true}]`, if the last release published from `master` is `1.0.0` then:
- Pushing a `BREAKING CHANGE` commit on the `beta` branch will release the version `2.0.0-beta.1` on the `beta` distribution channel
- Pushing either a `fix`, `feat` or a `BREAKING CHANGE` commit on the `beta` branch will release the version `2.0.0-beta.2` (then `2.0.0-beta.3`, `2.0.0-beta.4`, etc...) on the `beta` distribution channel
-
-#### Merging into a pre-release branch
-
-With the configuration `"branches": ["master", {"name": "beta", "prerelease": true}]`, if the last release published from `master` is `1.0.0` and the last one published from `beta` is `2.0.0-beta.1` then:
- Pushing a `fix` commit on the `master` branch will release the version `1.0.1` on the default distribution channel
- Merging the branch `master` into `beta` will release the version `2.0.0-beta.2` on the `beta` distribution channel
@@ -1,11 +1,8 @@
-const {pick} = require('lodash');
+const {template, pick} = require('lodash');
 const marked = require('marked');
 const TerminalRenderer = require('marked-terminal');
 const envCi = require('env-ci');
 const hookStd = require('hook-std');
-const pEachSeries = require('p-each-series');
-const semver = require('semver');
-const AggregateError = require('aggregate-error');
 const pkg = require('./package.json');
 const hideSensitive = require('./lib/hide-sensitive');
 const getConfig = require('./lib/get-config');
@@ -13,18 +10,15 @@ const verify = require('./lib/verify');
 const getNextVersion = require('./lib/get-next-version');
 const getCommits = require('./lib/get-commits');
 const getLastRelease = require('./lib/get-last-release');
-const getReleasesToAdd = require('./lib/get-releases-to-add');
-const {extractErrors, makeTag} = require('./lib/utils');
+const {extractErrors} = require('./lib/utils');
 const getGitAuthUrl = require('./lib/get-git-auth-url');
-const getBranches = require('./lib/branches');
 const getLogger = require('./lib/get-logger');
-const {verifyAuth, isBranchUpToDate, getGitHead, tag, push} = require('./lib/git');
+const {fetch, verifyAuth, isBranchUpToDate, getGitHead, tag, push} = require('./lib/git');
 const getError = require('./lib/get-error');
 const {COMMIT_NAME, COMMIT_EMAIL} = require('./lib/definitions/constants');

 marked.setOptions({renderer: new TerminalRenderer()});

-/* eslint complexity: ["warn", 25] */
 async function run(context, plugins) {
  const {cwd, env, options, logger} = context;
  const {isCi, branch: ciBranch, isPr} = envCi({env, cwd});
@@ -50,38 +44,32 @@ async function run(context, plugins) {
    return false;
  }

-  // Verify config
-  await verify(context);
-
-  context.branches = await getBranches(context);
-  context.branch = context.branches.find(({name}) => name === ciBranch);
-
-  if (!context.branch) {
+  if (ciBranch !== options.branch) {
    logger.log(
-      `This test run was triggered on the branch ${ciBranch}, while semantic-release is configured to only publish from ${context.branches
-        .map(({name}) => name)
-        .join(', ')}, 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' : ''}`
  );

+  await verify(context);
+
  options.repositoryUrl = await getGitAuthUrl(context);

  try {
    try {
-      await verifyAuth(options.repositoryUrl, context.branch.name, {cwd, env});
+      await verifyAuth(options.repositoryUrl, options.branch, {cwd, env});
    } catch (error) {
-      if (!(await isBranchUpToDate(context.branch.name, {cwd, env}))) {
+      if (!(await isBranchUpToDate(options.branch, {cwd, env}))) {
        logger.log(
-          `The local branch ${
-            context.branch.name
-          } is behind the remote one, therefore a new version won't be published.`
+          `The local branch ${options.branch} is behind the remote one, therefore a new version won't be published.`
        );
        return false;
      }
+
      throw error;
    }
  } catch (error) {
@@ -93,65 +81,21 @@ async function run(context, plugins) {

  await plugins.verifyConditions(context);

-  const releasesToAdd = getReleasesToAdd(context);
-  const errors = [];
-  context.releases = [];
-
-  await pEachSeries(releasesToAdd, async ({lastRelease, currentRelease, nextRelease}) => {
-    if (context.branch['merge-range'] && !semver.satisfies(nextRelease.version, context.branch['merge-range'])) {
-      errors.push(getError('EINVALIDMAINTENANCEMERGE', {nextRelease, branch: context.branch}));
-      return;
-    }
-
-    const commits = await getCommits({...context, lastRelease, nextRelease});
-    nextRelease.notes = await plugins.generateNotes({...context, commits, lastRelease, nextRelease});
-
-    logger.log('Create tag %s', nextRelease.gitTag);
-    await tag(nextRelease.gitTag, nextRelease.gitHead, {cwd, env});
-    await push(options.repositoryUrl, {cwd, env});
-    context.branch.tags.push({
-      version: nextRelease.version,
-      channel: nextRelease.channel,
-      gitTag: nextRelease.gitTag,
-      gitHead: nextRelease.gitHead,
-    });
-
-    const releases = await plugins.addChannel({...context, commits, lastRelease, currentRelease, nextRelease});
-    context.releases.push(...releases);
-    await plugins.success({...context, lastRelease, commits, nextRelease, releases});
-  });
-
-  if (errors.length > 0) {
-    throw new AggregateError(errors);
-  }
+  await fetch(options.repositoryUrl, {cwd, env});

  context.lastRelease = await getLastRelease(context);
-
  context.commits = await getCommits(context);

-  const nextRelease = {
-    type: await plugins.analyzeCommits(context),
-    channel: context.branch.channel,
-    gitHead: await getGitHead({cwd, env}),
-  };
+  const nextRelease = {type: await plugins.analyzeCommits(context), gitHead: await getGitHead({cwd, env})};
+
  if (!nextRelease.type) {
    logger.log('There are no relevant changes, so no new version is released.');
-    return context.releases.length > 0 ? {releases: context.releases} : false;
+    return false;
  }

  context.nextRelease = nextRelease;
  nextRelease.version = getNextVersion(context);
-  nextRelease.gitTag = makeTag(options.tagFormat, nextRelease.version, nextRelease.channel);
-  nextRelease.name = makeTag(options.tagFormat, nextRelease.version);
-
-  if (context.branch.type !== 'prerelease' && !semver.satisfies(nextRelease.version, context.branch.range)) {
-    throw getError('EINVALIDNEXTVERSION', {
-      ...context,
-      validBranches: context.branches.filter(
-        ({type, accept}) => type !== 'prerelease' && accept.includes(nextRelease.type)
-      ),
-    });
-  }
+  nextRelease.gitTag = template(options.tagFormat)({version: nextRelease.version});

  await plugins.verifyRelease(context);

@@ -163,12 +107,12 @@ async function run(context, plugins) {
    logger.warn(`Skip ${nextRelease.gitTag} tag creation in dry-run mode`);
  } else {
    // Create the tag before calling the publish plugins as some require the tag to exists
-    await tag(nextRelease.gitTag, nextRelease.gitHead, {cwd, env});
+    await tag(nextRelease.gitTag, {cwd, env});
    await push(options.repositoryUrl, {cwd, env});
    logger.success(`Created tag ${nextRelease.gitTag}`);
  }

-  context.releases.push(...(await plugins.publish(context)));
+  context.releases = await plugins.publish(context);

  await plugins.success(context);

@@ -1,18 +0,0 @@
-const {isString, remove, omit, mapValues, template} = require('lodash');
-const micromatch = require('micromatch');
-const {getBranches} = require('../git');
-
-module.exports = async ({cwd}, branches) => {
-  const gitBranches = await getBranches({cwd});
-
-  return branches.reduce(
-    (branches, branch) => [
-      ...branches,
-      ...remove(gitBranches, name => micromatch(gitBranches, branch.name).includes(name)).map(name => ({
-        name,
-        ...mapValues(omit(branch, 'name'), value => (isString(value) ? template(value)({name}) : value)),
-      })),
-    ],
-    []
-  );
-};
@@ -1,39 +0,0 @@
-const {template, escapeRegExp} = require('lodash');
-const semver = require('semver');
-const pReduce = require('p-reduce');
-const debug = require('debug')('semantic-release:get-tags');
-const {getTags, isRefInHistory, getTagHead} = require('../../lib/git');
-
-module.exports = async ({cwd, env, options: {tagFormat}}, branches) => {
-  // 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`.
-  const tagRegexp = `^${escapeRegExp(template(tagFormat)({version: ' '})).replace(' ', '(.[^@]+)@?(.+)?')}`;
-  const tags = (await getTags({cwd, env}))
-    .map(tag => {
-      const [, version, channel] = tag.match(tagRegexp) || [];
-      return {gitTag: tag, version, channel};
-    })
-    .filter(({version}) => version && semver.valid(semver.clean(version)));
-
-  debug('found tags: %o', tags);
-
-  return pReduce(
-    branches,
-    async (branches, branch) => {
-      const branchTags = await pReduce(
-        tags,
-        async (tags, {gitTag, ...rest}) =>
-          (await isRefInHistory(gitTag, branch.name, true, {cwd, env}))
-            ? [...tags, {...rest, gitTag, gitHead: await getTagHead(gitTag, {cwd, env})}]
-            : tags,
-        []
-      );
-
-      debug('found tags for branch %s: %o', branch.name, branchTags);
-      return [...branches, {...branch, tags: branchTags}];
-    },
-    []
-  );
-};
@@ -1,67 +0,0 @@
-const {isString, isRegExp} = require('lodash');
-const AggregateError = require('aggregate-error');
-const pEachSeries = require('p-each-series');
-const DEFINITIONS = require('../definitions/branches');
-const getError = require('../get-error');
-const {fetch, verifyBranchName} = require('../git');
-const expand = require('./expand');
-const getTags = require('./get-tags');
-const normalize = require('./normalize');
-
-module.exports = async context => {
-  const {cwd, env} = context;
-
-  const remoteBranches = await expand(
-    context,
-    context.options.branches.map(branch => (isString(branch) || isRegExp(branch) ? {name: branch} : branch))
-  );
-
-  await pEachSeries(remoteBranches, async ({name}) => {
-    await fetch(name, {cwd, env});
-  });
-
-  const branches = await getTags(context, remoteBranches);
-
-  const errors = [];
-  const branchesByType = Object.entries(DEFINITIONS).reduce(
-    (branchesByType, [type, {filter}]) => ({[type]: branches.filter(filter), ...branchesByType}),
-    {}
-  );
-
-  const result = Object.entries(DEFINITIONS).reduce((result, [type, {branchesValidator, branchValidator}]) => {
-    branchesByType[type].forEach(branch => {
-      if (branchValidator && !branchValidator(branch)) {
-        errors.push(getError(`E${type.toUpperCase()}BRANCH`, {branch}));
-      }
-    });
-
-    const branchesOfType = normalize[type](branchesByType);
-
-    if (!branchesValidator(branchesOfType)) {
-      errors.push(getError(`E${type.toUpperCase()}BRANCHES`, {branches: branchesOfType}));
-    }
-
-    return {...result, [type]: branchesOfType};
-  }, {});
-
-  const duplicates = [...branches]
-    .map(branch => branch.name)
-    .sort()
-    .filter((val, idx, arr) => arr[idx] === arr[idx + 1] && arr[idx] !== arr[idx - 1]);
-
-  if (duplicates.length > 0) {
-    errors.push(getError('EDUPLICATEBRANCHES', {duplicates}));
-  }
-
-  await pEachSeries(branches, async branch => {
-    if (!(await verifyBranchName(branch.name))) {
-      errors.push(getError('EINVALIDBRANCHNAME', branch));
-    }
-  });
-
-  if (errors.length > 0) {
-    throw new AggregateError(errors);
-  }
-
-  return [...result.maintenance, ...result.release, ...result.prerelease];
-};
@@ -1,110 +0,0 @@
-const {sortBy} = require('lodash');
-const semver = require('semver');
-const semverDiff = require('semver-diff');
-const {FIRST_RELEASE, RELEASE_TYPE} = require('../definitions/constants');
-const {
-  tagsToVersions,
-  isMajorRange,
-  getUpperBound,
-  getLowerBound,
-  highest,
-  lowest,
-  getLatestVersion,
-  getFirstVersion,
-  getRange,
-} = require('../utils');
-
-function maintenance({maintenance, release}) {
-  return sortBy(
-    maintenance.map(({name, range, channel, ...rest}) => ({
-      ...rest,
-      name,
-      range: range || name,
-      channel: channel || name,
-    })),
-    'range'
-  ).map(({name, range, tags, ...rest}, idx, branches) => {
-    const versions = tagsToVersions(tags);
-    // Find the lower bound based on Maintenance branches
-    const maintenanceMin =
-      // If the current branch has a major range (1.x or 1.x.x) and the previous doesn't
-      isMajorRange(range) && branches[idx - 1] && !isMajorRange(branches[idx - 1].range)
-        ? // Then the lowest bound is the upper bound of the previous branch range
-          getUpperBound(branches[idx - 1].range)
-        : // Otherwise the lowest bound is the lowest bound of the current branch range
-          getLowerBound(range);
-    // The actual lower bound is the highest version between the current branch last release and `maintenanceMin`
-    const min = highest(getLatestVersion(versions) || FIRST_RELEASE, maintenanceMin);
-    // Determine the first release of the default branch not present in any maintenance branch
-    const base =
-      (release[0] &&
-        (getFirstVersion(tagsToVersions(release[0].tags), branches) ||
-          getLatestVersion(tagsToVersions(release[0].tags)))) ||
-      FIRST_RELEASE;
-    // The upper bound is the lowest version between the `base` version and the upper bound of the current branch range
-    const max = lowest(base, getUpperBound(range));
-    const diff = semverDiff(min, max);
-    return {
-      ...rest,
-      type: 'maintenance',
-      name,
-      tags,
-      range: getRange(min, max),
-      accept: diff ? RELEASE_TYPE.slice(0, RELEASE_TYPE.indexOf(diff)) : [],
-      'merge-range': getRange(maintenanceMin, getUpperBound(range)),
-    };
-  });
-}
-
-function release({release}) {
-  if (release.length === 0) {
-    return release;
-  }
-  const breakpoints = release.length > 2 ? ['minor', 'major'] : ['major'];
-
-  // The intial bound is the last release from the base branch of `FIRST_RELEASE` (1.0.0)
-  let bound = getLatestVersion(tagsToVersions(release[0].tags)) || FIRST_RELEASE;
-
-  return release.map(({name, tags, channel, ...rest}, idx) => {
-    const versions = tagsToVersions(tags);
-    // The lower bound is the highest version between the current branch last release and the previous branch upper bound (`bound`)
-    const min = highest(getLatestVersion(versions), bound);
-    if (release.length - 1 === idx) {
-      // If the current branch is the last one of the release branch, there is no upper bound
-      bound = undefined;
-    } else {
-      // The default upper bound is the lower bound increment with the release type of the current branch position
-      const upperBound = semver.inc(min, breakpoints[idx]);
-      // Find the lowest version that is present on the current branch but none of the previous ones
-      const nextFirstVersion = getFirstVersion(tagsToVersions(release[idx + 1].tags), release.slice(0, idx + 1));
-      // The upper bound is the lowest version between `nextFirstVersion` and the default upper bound
-      bound = lowest(nextFirstVersion, upperBound);
-    }
-    const diff = bound ? semverDiff(min, bound) : null;
-    return {
-      ...rest,
-      channel: idx === 0 ? channel : channel || name,
-      tags,
-      type: 'release',
-      name,
-      range: getRange(min, bound),
-      accept: bound ? RELEASE_TYPE.slice(0, RELEASE_TYPE.indexOf(diff)) : RELEASE_TYPE,
-    };
-  });
-}
-
-function prerelease({prerelease}) {
-  return prerelease.map(({name, prerelease, channel, tags, ...rest}) => {
-    const preid = prerelease === true ? name : prerelease;
-    return {
-      ...rest,
-      channel: channel || name,
-      type: 'prerelease',
-      name,
-      prerelease: preid,
-      tags,
-    };
-  });
-}
-
-module.exports = {maintenance, release, prerelease};
@@ -1,23 +0,0 @@
-const {isUndefined, uniqBy} = require('lodash');
-const semver = require('semver');
-const {isMaintenanceRange} = require('../utils');
-
-const maintenance = {
-  filter: ({name, range}) => !isUndefined(range) || isMaintenanceRange(name),
-  branchValidator: ({range}) => (isUndefined(range) ? true : isMaintenanceRange(range)),
-  branchesValidator: branches => uniqBy(branches, ({range}) => semver.validRange(range)).length === branches.length,
-};
-
-const prerelease = {
-  filter: ({prerelease}) => !isUndefined(prerelease),
-  branchValidator: ({name, prerelease}) =>
-    Boolean(prerelease) && Boolean(semver.valid(`1.0.0-${prerelease === true ? name : prerelease}.1`)),
-  branchesValidator: branches => uniqBy(branches, 'prerelease').length === branches.length,
-};
-
-const release = {
-  filter: branch => !maintenance.filter(branch) && !prerelease.filter(branch),
-  branchesValidator: branches => branches.length <= 3 && branches.length > 0,
-};
-
-module.exports = {maintenance, prerelease, release};
@@ -1,9 +1,7 @@
-const RELEASE_TYPE = ['patch', 'minor', 'major'];
+const RELEASE_TYPE = ['prerelease', 'prepatch', 'patch', 'preminor', 'minor', 'premajor', 'major'];

 const FIRST_RELEASE = '1.0.0';

-const FIRSTPRERELEASE = '1';
-
 const COMMIT_NAME = 'semantic-release-bot';

 const COMMIT_EMAIL = 'semantic-release-bot@martynus.net';
@@ -17,7 +15,6 @@ const SECRET_MIN_SIZE = 5;
 module.exports = {
  RELEASE_TYPE,
  FIRST_RELEASE,
-  FIRSTPRERELEASE,
  COMMIT_NAME,
  COMMIT_EMAIL,
  RELEASE_NOTES_SEPARATOR,
@@ -1,14 +1,11 @@
-const url = require('url');
 const {inspect} = require('util');
-const {toLower, isString, trim} = require('lodash');
+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}`;
-const wordsList = words =>
-  `${words.slice(0, -1).join(', ')}${words.length > 1 ? ` or ${words[words.length - 1]}` : trim(words[0])}`;

 module.exports = {
  ENOGITREPO: ({cwd}) => ({
@@ -127,119 +124,4 @@ We recommend to report the issue to the \`${pluginName}\` authors, providing the
      'docs/developer-guide/plugin.md'
    )})`,
  }),
-  EADDCHANNELOUTPUT: ({result, pluginName}) => ({
-    message: 'A `addChannel` plugin returned an invalid value. It must return an `Object`.',
-    details: `The \`addChannel\` plugins must return an \`Object\`.
-
-The \`addChannel\` function of the \`${pluginName}\` returned \`${stringify(result)}\` instead.
-
-We recommend to report the issue to the \`${pluginName}\` authors, providing the following informations:
- The **semantic-release** version: \`${pkg.version}\`
- The **semantic-release** logs from your CI job
- The value returned by the plugin: \`${stringify(result)}\`
- A link to the **semantic-release** plugin developer guide: [${linkify('docs/developer-guide/plugin.md')}](${linkify(
-      'docs/developer-guide/plugin.md'
-    )})`,
-  }),
-  EINVALIDBRANCH: ({branch}) => ({
-    message: 'A branch is invalid in the `branches` configuration.',
-    details: `Each branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must be either a string, a regexp or an object with a \`name\` property.
-
-Your configuration for the problematic branch is \`${stringify(branch)}\`.`,
-  }),
-  EINVALIDBRANCHNAME: ({branch}) => ({
-    message: 'A branch name is invalid in the `branches` configuration.',
-    details: `Each branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must be a [valid Git reference](https://git-scm.com/docs/git-check-ref-format#_description).
-
-Your configuration for the problematic branch is \`${stringify(branch)}\`.`,
-  }),
-  EDUPLICATEBRANCHES: ({duplicates}) => ({
-    message: 'The `branches` configuration has duplicate branches.',
-    details: `Each branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must havea unique name.
-
-Your configuration contains duplicates for the following branch names: \`${stringify(duplicates)}\`.`,
-  }),
-  EMAINTENANCEBRANCH: ({branch}) => ({
-    message: 'A maintenance branch is invalid in the `branches` configuration.',
-    details: `Each maintenance branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must have a \`range\` property formatted like \`N.x\`, \`N.x.x\` or \`N.N.x\` (\`N\` is a number).
-
-Your configuration for the problematic branch is \`${stringify(branch)}\`.`,
-  }),
-  EMAINTENANCEBRANCHES: ({branches}) => ({
-    message: 'The maintenance branches are invalid in the `branches` configuration.',
-    details: `Each maintenance branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must have a unique \`range\` property.
-
-Your configuration for the problematic branches is \`${stringify(branches)}\`.`,
-  }),
-  ERELEASEBRANCHES: ({branches}) => ({
-    message: 'The release branches are invalid in the `branches` configuration.',
-    details: `A minimum of 1 and a maximum of 3 release branches are required in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}).
-
-Your configuration for the problematic branches is \`${stringify(branches)}\`.`,
-  }),
-  EPRERELEASEBRANCH: ({branch}) => ({
-    message: 'A pre-release branch configuration is invalid in the `branches` configuration.',
-    details: `Each pre-release branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must have a \`prerelease\` property valid per the [Semantic Versioning Specification](https://semver.org/#spec-item-9). If the \`prerelease\` property is set to \`true\`, then the \`name\` property is used instead.
-
-Your configuration for the problematic branch is \`${stringify(branch)}\`.`,
-  }),
-  EPRERELEASEBRANCHES: ({branches}) => ({
-    message: 'The pre-release branches are invalid in the `branches` configuration.',
-    details: `Each pre-release branch in the [branches configuration](${linkify(
-      'docs/usage/configuration.md#branches'
-    )}) must have a unique \`prerelease\` property. If the \`prerelease\` property is set to \`true\`, then the \`name\` property is used instead.
-
-Your configuration for the problematic branches is \`${stringify(branches)}\`.`,
-  }),
-  EINVALIDNEXTVERSION: ({nextRelease, branch, commits, validBranches}) => ({
-    message: `The release \`${nextRelease.version}\` on branch \`${
-      branch.name
-    }\` cannot be published as it is out of range.`,
-    details: `Based on the releases published on other branches, only versions within the range \`${
-      branch.range
-    }\` can be published from branch \`${branch.name}\`.
-
-The following commit${commits.length > 1 ? 's are' : ' is'} responsible for the invalid release:
-${commits.map(({commit: {short}, subject}) => `- ${subject} (${short})`).join('\n')}
-
-${
-      commits.length > 1 ? 'Those commits' : 'This commit'
-    } should be moved to a valid branch with [git merge](https://git-scm.com/docs/git-merge) or [git cherry-pick](https://git-scm.com/docs/git-cherry-pick) and removed from branch \`${
-      branch.name
-    }\` with [git revert](https://git-scm.com/docs/git-revert) or [git reset](https://git-scm.com/docs/git-reset).
-
-A valid branch could be ${wordsList(validBranches.map(({name}) => `\`${name}\``))}.
-
-See the [workflow configuration documentation](${linkify('docs/usage/workflow-configuration.md')}) for more details.`,
-  }),
-  EINVALIDMAINTENANCEMERGE: ({nextRelease, branch}) => ({
-    message: `The release \`${nextRelease.version}\` on branch \`${
-      branch.name
-    }\` cannot be published as it is out of range.`,
-    details: `Only releases within the range \`${branch['merge-range']}\` can be merged into the maintenance branch \`${
-      branch.name
-    }\` and published to the \`${nextRelease.channel}\` distribution channel.
-
-The branch \`${
-      branch.name
-    }\` head should be [reset](https://git-scm.com/docs/git-reset) to a previous commit so the commit with tag \`${
-      nextRelease.gitTag
-    }\` is removed from the branch history.
-
-See the [workflow configuration documentation](${linkify('docs/usage/workflow-configuration.md')}) for more details.`,
-  }),
 };
@@ -59,6 +59,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,22 +72,9 @@ module.exports = {
    pipelineConfig: () => ({
      // Add `nextRelease` and plugin properties to published release
      transform: (release, step, {nextRelease}) => ({
-        ...nextRelease,
-        ...(release || {}),
-        ...(release === false ? {} : step),
-      }),
-    }),
-  },
-  addChannel: {
-    required: false,
-    dryRun: false,
-    outputValidator: output => !output || isPlainObject(output),
-    pipelineConfig: () => ({
-      // Add `nextRelease` and plugin properties to published release
-      transform: (release, step, {nextRelease}) => ({
-        ...nextRelease,
-        ...(release || {}),
-        ...(release === false ? {} : step),
+        ...(release === false ? {} : nextRelease),
+        ...release,
+        ...step,
      }),
    }),
  },
@@ -1,5 +1,6 @@
+const gitLogParser = require('git-log-parser');
+const getStream = require('get-stream');
 const debug = require('debug')('semantic-release:get-commits');
-const {getCommits} = require('./git');

 /**
 * Retrieve the list of commits on the current branch since the commit sha associated with the last release, or all the commits of the current branch if there is no last released version.
@@ -8,15 +9,21 @@ const {getCommits} = require('./git');
 *
 * @return {Promise<Array<Object>>} The list of commits on the branch `branch` since the last release.
 */
-module.exports = async ({cwd, env, lastRelease: {gitHead: from}, nextRelease: {gitHead: to = 'HEAD'} = {}, logger}) => {
-  if (from) {
-    debug('Use from: %s', from);
+module.exports = async ({cwd, env, lastRelease: {gitHead}, logger}) => {
+  if (gitHead) {
+    debug('Use gitHead: %s', gitHead);
  } else {
    logger.log('No previous release found, retrieving all commits');
  }

-  const commits = await getCommits(from, to, {cwd, env});
-
+  Object.assign(gitLogParser.fields, {hash: 'H', message: 'B', gitTags: 'd', committerDate: {key: 'ci', type: Date}});
+  const commits = (await getStream.array(
+    gitLogParser.parse({_: `${gitHead ? gitHead + '..' : ''}HEAD`}, {cwd, env: {...process.env, ...env}})
+  )).map(commit => {
+    commit.message = commit.message.trim();
+    commit.gitTags = commit.gitTags.trim();
+    return commit;
+  });
  logger.log(`Found ${commits.length} commits since last release`);
  debug('Parsed commits: %o', commits);
  return commits;
@@ -30,6 +30,7 @@ module.exports = async (context, opts) => {
  if (options.ci === false) {
    options.noCi = true;
  }
+
  const pluginsPath = {};
  let extendPaths;
  ({extends: extendPaths, ...options} = options);
@@ -65,14 +66,7 @@ module.exports = async (context, opts) => {

  // Set default options values if not defined yet
  options = {
-    branches: [
-      '+([1-9])?(.{+([1-9]),x}).x',
-      'master',
-      'next',
-      'next-major',
-      {name: 'beta', prerelease: true},
-      {name: 'alpha', prerelease: true},
-    ],
+    branch: 'master',
    repositoryUrl: (await pkgRepoUrl({normalize: false, cwd})) || (await repoUrl({cwd, env})),
    tagFormat: `v\${version}`,
    plugins: [
@@ -83,7 +77,6 @@ module.exports = async (context, opts) => {
    ],
    // Remove `null` and `undefined` options so they can be replaced with default ones
    ...pickBy(options, option => !isNil(option)),
-    ...(options.branches ? {branches: castArray(options.branches)} : {}),
  };

  debug('options values: %O', options);
@@ -92,6 +85,6 @@ module.exports = async (context, opts) => {
 };

 async function pkgRepoUrl(opts) {
-  const {pkg} = await readPkgUp(opts);
+  const {package: pkg} = (await readPkgUp(opts)) || {};
  return pkg && (isPlainObject(pkg.repository) ? pkg.repository.url : pkg.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
@@ -24,7 +14,19 @@ const GIT_TOKENS = {
 *
 * @return {String} The formatted Git repository URL.
 */
-module.exports = async ({cwd, env, branch, options: {repositoryUrl}}) => {
+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);

@@ -38,13 +40,13 @@ module.exports = async ({cwd, env, branch, options: {repositoryUrl}}) => {

  // Test if push is allowed without transforming the URL (e.g. is ssh keys are set up)
  try {
-    await verifyAuth(repositoryUrl, branch.name, {cwd, env});
+    await verifyAuth(repositoryUrl, branch, {cwd, env});
  } catch (error) {
    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),
@@ -1,6 +1,8 @@
-const {isUndefined} = require('lodash');
+const {escapeRegExp, template} = require('lodash');
 const semver = require('semver');
-const {makeTag} = require('./utils');
+const pLocate = require('p-locate');
+const debug = require('debug')('semantic-release:get-last-release');
+const {getTags, isRefInHistory, getTagHead} = require('./git');

 /**
 * Last release.
@@ -13,27 +15,37 @@ const {makeTag} = require('./utils');
 /**
 * Determine the Git tag and version of the last tagged release.
 *
- * - Filter out the branch tags that are not valid semantic version
+ * - Obtain all the tags referencing commits in the current branch history
+ * - Filter out the ones that are not valid semantic version or doesn't match the `tagFormat`
 * - Sort the versions
 * - Retrive the highest version
 *
 * @param {Object} context semantic-release context.
- * @param {Object} params Function parameters.
- * @param {Object} params.before Find only releases with version number lower than this version.
 *
- * @return {LastRelease} The last tagged release or empty object if none is found.
+ * @return {Promise<LastRelease>} The last tagged release or `undefined` if none is found.
 */
-module.exports = ({branch: {name, tags, type}, options: {tagFormat}, logger}, {before} = {}) => {
-  const [{version, gitTag, gitHead, channel} = {}] = tags
-    .filter(tag => type === 'prerelease' || !semver.prerelease(tag.version))
-    .filter(tag => isUndefined(before) || semver.lt(tag.version, before))
+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 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]}))
+    .filter(
+      tag => tag.version && semver.valid(semver.clean(tag.version)) && !semver.prerelease(semver.clean(tag.version))
+    )
    .sort((a, b) => semver.rcompare(a.version, b.version));

-  if (gitTag) {
-    logger.log(`Found git tag ${gitTag} associated with version ${version} on branch ${name}`);
-    return {version, gitTag, gitHead, channel, name: makeTag(tagFormat, version)};
+  debug('found tags: %o', tags);
+
+  const tag = await pLocate(tags, tag => isRefInHistory(tag.gitTag, {cwd, env}), {preserveOrder: true});
+
+  if (tag) {
+    logger.log(`Found git tag ${tag.gitTag} associated with version ${tag.version}`);
+    return {gitHead: await getTagHead(tag.gitTag, {cwd, env}), ...tag};
  }

-  logger.log(`No git tag version found on branch ${name}`);
+  logger.log('No git tag version found');
  return {};
 };
@@ -1,18 +1,13 @@
 const semver = require('semver');
-const {FIRST_RELEASE, FIRSTPRERELEASE} = require('./definitions/constants');
+const {FIRST_RELEASE} = require('./definitions/constants');

-module.exports = ({branch, nextRelease: {type}, lastRelease, logger}) => {
+module.exports = ({nextRelease: {type}, lastRelease, logger}) => {
  let version;
  if (lastRelease.version) {
-    version =
-      branch.type === 'prerelease'
-        ? semver.prerelease(lastRelease.version)
-          ? semver.inc(lastRelease.version, 'prerelease')
-          : `${semver.inc(lastRelease.version, type)}-${branch.prerelease}.${FIRSTPRERELEASE}`
-        : semver.inc(lastRelease.version, type);
-    logger.log('The next release version is %s', version);
+    version = semver.inc(lastRelease.version, type);
+    logger.log(`The next release version is ${version}`);
  } else {
-    version = branch.type === 'prerelease' ? `${FIRST_RELEASE}-${branch.prerelease}.${FIRSTPRERELEASE}` : FIRST_RELEASE;
+    version = FIRST_RELEASE;
    logger.log(`There is no previous release, the next release version is ${version}`);
  }

@@ -1,64 +0,0 @@
-const {uniq} = require('lodash');
-const semver = require('semver');
-const semverDiff = require('semver-diff');
-const getLastRelease = require('./get-last-release');
-const {makeTag} = require('./utils');
-
-/**
- * Find releases that have been merged from from a higher branch but not added on the channel of the current branch.
- *
- * @param {Object} context semantic-release context.
- *
- * @return {Array<Object>} Last release and next release to be added on the channel of the current branch.
- */
-module.exports = context => {
-  const {
-    branch,
-    branches,
-    options: {tagFormat},
-  } = context;
-
-  return (
-    branches
-      // Consider only releases of higher branches
-      .slice(branches.findIndex(({name}) => name === branch.name) + 1)
-      // Exclude prerelease branches
-      .filter(({type}) => type !== 'prerelease')
-      // Find higher branch releases merged to building branch but not released on associated channel
-      .reduce(
-        (releases, higherBranch) => [
-          ...releases,
-          // For all unique release version of the higher branch merged on current branch
-          ...uniq(branch.tags.filter(({channel}) => channel === higherBranch.channel))
-            // Find ones that are not released on the building branch channel
-            .filter(tag =>
-              branch.tags.every(
-                ({version, channel}) =>
-                  version !== tag.version || channel === higherBranch.channel || channel !== branch.channel
-              )
-            )
-            // Sort in ascending order to add the most recent release last
-            .sort((a, b) => semver.compare(a.version, b.version))
-            // Construct the last and next release to add to the building branch channel
-            .map(({version, gitHead, gitTag}) => {
-              const lastRelease = getLastRelease(context, {before: version});
-              const type = lastRelease.version ? semverDiff(lastRelease.version, version) : 'major';
-              const name = makeTag(tagFormat, version);
-              return {
-                lastRelease,
-                currentRelease: {type, version, channel: higherBranch.channel, gitTag, name, gitHead},
-                nextRelease: {
-                  type,
-                  version,
-                  channel: branch.channel,
-                  gitTag: makeTag(tagFormat, version, branch.channel),
-                  name,
-                  gitHead,
-                },
-              };
-            }),
-        ],
-        []
-      )
-  );
-};
@@ -1,22 +1,17 @@
-const {matches, pick, memoize} = require('lodash');
-const gitLogParser = require('git-log-parser');
-const getStream = require('get-stream');
 const execa = require('execa');
 const debug = require('debug')('semantic-release:git');

-Object.assign(gitLogParser.fields, {hash: 'H', message: 'B', gitTags: 'd', committerDate: {key: 'ci', type: Date}});
-
 /**
 * Get the commit sha for a given tag.
 *
 * @param {String} tagName Tag name for which to retrieve the commit sha.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 *
- * @return {String} The commit sha of the tag in parameter or `null`.
+ * @return {string} The commit sha of the tag in parameter or `null`.
 */
 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);
  }
@@ -31,74 +26,26 @@ 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);
 }

 /**
- * Retrieve a range of commits.
- *
- * @param {String} from to includes all commits made after this sha (does not include this sha).
- * @param {String} to to includes all commits made before this sha (also include this sha).
- * @param {Object} [execaOpts] Options to pass to `execa`.
- * @return {Promise<Array<Object>>} The list of commits between `from` and `to`.
- */
-async function getCommits(from, to, execaOpts) {
-  return (await getStream.array(
-    gitLogParser.parse(
-      {_: `${from ? from + '..' : ''}${to}`},
-      {cwd: execaOpts.cwd, env: {...process.env, ...execaOpts.env}}
-    )
-  )).map(({message, gitTags, ...commit}) => ({...commit, message: message.trim(), gitTags: gitTags.trim()}));
-}
-
-/**
- * Get all the repository branches.
- *
- * @param {Object} [execaOpts] Options to pass to `execa`.
- *
- * @return {Array<String>} List of git branches.
- * @throws {Error} If the `git` command fails.
- */
-async function getBranches(execaOpts) {
-  return (await execa.stdout('git', ['ls-remote', '--heads', 'origin'], execaOpts))
-    .split('\n')
-    .map(branch => branch.match(/^.+refs\/heads\/(.+)$/)[1])
-    .filter(Boolean);
-}
-
-const getBranchCommits = memoize((branch, execaOpts) =>
-  getStream.array(gitLogParser.parse({_: branch}, {cwd: execaOpts.cwd, env: {...process.env, ...execaOpts.env}}))
-);
-
-/**
- * Verify if the `ref` is in the direct history of a given branch.
+ * Verify if the `ref` is in the direct history of the current branch.
 *
 * @param {String} ref The reference to look for.
- * @param {String} branch The branch for which to check if the `ref` is in history.
- * @param {Boolean} findRebasedTags Weither consider in history tags associated with a commit that was rebased to another branch (i.e. GitHub Rebase and Merge feature).
 * @param {Object} [execaOpts] Options to pass to `execa`.
 *
 * @return {Boolean} `true` if the reference is in the history of the current branch, falsy otherwise.
 */
-async function isRefInHistory(ref, branch, findRebasedTags, execaOpts) {
-  if (!(await isRefExists(branch, execaOpts))) {
-    return false;
-  }
-
+async function isRefInHistory(ref, execaOpts) {
  try {
-    await execa('git', ['merge-base', '--is-ancestor', ref, branch], execaOpts);
+    await execa('git', ['merge-base', '--is-ancestor', ref, 'HEAD'], execaOpts);
    return true;
  } catch (error) {
    if (error.code === 1) {
-      if (findRebasedTags) {
-        const [tagCommit] = await getStream.array(
-          gitLogParser.parse({_: ref, n: '1'}, {cwd: execaOpts.cwd, env: {...process.env, ...execaOpts.env}})
-        );
-        return (await getBranchCommits(branch, execaOpts)).some(matches(pick(tagCommit, ['message', 'author'])));
-      }
      return false;
    }

@@ -107,49 +54,17 @@ async function isRefInHistory(ref, branch, findRebasedTags, execaOpts) {
  }
 }

-/**
- * Verify if the `ref` exits
- *
- * @param {String} ref The reference to verify.
- * @param {Object} [execaOpts] Options to pass to `execa`.
- *
- * @return {Boolean} `true` if the reference exists, falsy otherwise.
- */
-async function isRefExists(ref, execaOpts) {
-  try {
-    return (await execa('git', ['rev-parse', '--verify', ref], execaOpts)).code === 0;
-  } catch (error) {
-    debug(error);
-  }
-}
-
 /**
 * Unshallow the git repository if necessary and fetch all the tags.
 *
- * @param {String} branch The repository branch to fetch.
+ * @param {String} repositoryUrl The remote repository URL.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 */
-async function fetch(branch, execaOpts) {
-  const isLocalExists =
-    (await execa('git', ['rev-parse', '--verify', branch], {...execaOpts, reject: false})).code === 0;
-
+async function fetch(repositoryUrl, execaOpts) {
  try {
-    await execa(
-      'git',
-      [
-        'fetch',
-        '--unshallow',
-        '--tags',
-        ...(isLocalExists ? [] : ['origin', `+refs/heads/${branch}:refs/heads/${branch}`]),
-      ],
-      execaOpts
-    );
+    await execa('git', ['fetch', '--unshallow', '--tags', repositoryUrl], execaOpts);
  } catch (error) {
-    await execa(
-      'git',
-      ['fetch', '--tags', ...(isLocalExists ? [] : ['origin', `+refs/heads/${branch}:refs/heads/${branch}`])],
-      execaOpts
-    );
+    await execa('git', ['fetch', '--tags', repositoryUrl], execaOpts);
  }
 }

@@ -160,8 +75,8 @@ async function fetch(branch, 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;
 }

 /**
@@ -173,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);
  }
@@ -198,7 +113,7 @@ async function isGitRepo(execaOpts) {
 * Verify the write access authorization to remote repository with push dry-run.
 *
 * @param {String} repositoryUrl The remote repository URL.
- * @param {String} branch The repository branch for which to verify write access.
+ * @param {String} branch The repositoru branch for which to verify write access.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 *
 * @throws {Error} if not authorized to push.
@@ -216,13 +131,12 @@ async function verifyAuth(repositoryUrl, branch, execaOpts) {
 * Tag the commit head on the local repository.
 *
 * @param {String} tagName The name of the tag.
- * @param {String} ref The Git reference to tag.
 * @param {Object} [execaOpts] Options to pass to `execa`.
 *
 * @throws {Error} if the tag creation failed.
 */
-async function tag(tagName, ref, execaOpts) {
-  await execa('git', ['tag', tagName, ref], execaOpts);
+async function tag(tagName, execaOpts) {
+  await execa('git', ['tag', tagName], execaOpts);
 }

 /**
@@ -253,22 +167,6 @@ async function verifyTagName(tagName, execaOpts) {
  }
 }

-/**
- * Verify a branch name is a valid Git reference.
- *
- * @param {String} branch the branch name to verify.
- * @param {Object} [execaOpts] Options to pass to `execa`.
- *
- * @return {Boolean} `true` if valid, falsy otherwise.
- */
-async function verifyBranchName(branch, execaOpts) {
-  try {
-    return (await execa('git', ['check-ref-format', `refs/heads/${branch}`], execaOpts)).code === 0;
-  } catch (error) {
-    debug(error);
-  }
-}
-
 /**
 * Verify the local branch is up to date with the remote one.
 *
@@ -278,9 +176,9 @@ async function verifyBranchName(branch, 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], branch, false, execaOpts);
+    return await isRefInHistory(remoteHead.match(/^(\w+)?/)[1], execaOpts);
  } catch (error) {
    debug(error);
  }
@@ -289,10 +187,7 @@ async function isBranchUpToDate(branch, execaOpts) {
 module.exports = {
  getTagHead,
  getTags,
-  getCommits,
-  getBranches,
  isRefInHistory,
-  isRefExists,
  fetch,
  getGitHead,
  repoUrl,
@@ -302,5 +197,4 @@ module.exports = {
  push,
  verifyTagName,
  isBranchUpToDate,
-  verifyBranchName,
 };
@@ -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 || {}];
 }

@@ -1,5 +1,4 @@
-const {isFunction, union, template} = require('lodash');
-const semver = require('semver');
+const {isFunction} = require('lodash');
 const hideSensitive = require('./hide-sensitive');

 function extractErrors(err) {
@@ -18,71 +17,4 @@ function hideSensitiveValues(env, objs) {
  });
 }

-function tagsToVersions(tags) {
-  return tags.map(({version}) => version);
-}
-
-function isMajorRange(range) {
-  return /^\d+\.x(?:\.x)?$/i.test(range);
-}
-
-function isMaintenanceRange(range) {
-  return /^\d+\.(?:\d+|x)(?:\.x)?$/i.test(range);
-}
-
-function getUpperBound(range) {
-  return semver.valid(range) ? range : ((semver.validRange(range) || '').match(/<(\d\.\d\.\d)$/) || [])[1];
-}
-
-function getLowerBound(range) {
-  return ((semver.validRange(range) || '').match(/(\d\.\d\.\d)/) || [])[1];
-}
-
-function highest(version1, version2) {
-  return version1 && version2 ? (semver.gt(version1, version2) ? version1 : version2) : version1 || version2;
-}
-
-function lowest(version1, version2) {
-  return version1 && version2 ? (semver.lt(version1, version2) ? version1 : version2) : version1 || version2;
-}
-
-function getLatestVersion(versions, {withPrerelease} = {}) {
-  return versions.filter(version => withPrerelease || !semver.prerelease(version)).sort(semver.rcompare)[0];
-}
-
-function getEarliestVersion(versions, {withPrerelease} = {}) {
-  return versions.filter(version => withPrerelease || !semver.prerelease(version)).sort(semver.compare)[0];
-}
-
-function getFirstVersion(versions, lowerBranches) {
-  const lowerVersion = union(...lowerBranches.map(({tags}) => tagsToVersions(tags))).sort(semver.rcompare);
-  if (lowerVersion[0]) {
-    return versions.sort(semver.compare).find(version => semver.gt(version, lowerVersion[0]));
-  }
-  return getEarliestVersion(versions);
-}
-
-function getRange(min, max) {
-  return `>=${min}${max ? ` <${max}` : ''}`;
-}
-
-function makeTag(tagFormat, version, channel) {
-  return template(tagFormat)({version: `${version}${channel ? `@${channel}` : ''}`});
-}
-
-module.exports = {
-  extractErrors,
-  hideSensitiveValues,
-  tagsToVersions,
-  isMajorRange,
-  isMaintenanceRange,
-  getUpperBound,
-  getLowerBound,
-  highest,
-  lowest,
-  getLatestVersion,
-  getEarliestVersion,
-  getFirstVersion,
-  getRange,
-  makeTag,
-};
+module.exports = {extractErrors, hideSensitiveValues};
@@ -1,9 +1,9 @@
-const {template, isString, isPlainObject} = require('lodash');
+const {template} = require('lodash');
 const AggregateError = require('aggregate-error');
 const {isGitRepo, verifyTagName} = require('./git');
 const getError = require('./get-error');

-module.exports = async ({cwd, env, options: {repositoryUrl, tagFormat, branches}}) => {
+module.exports = async ({cwd, env, options: {repositoryUrl, tagFormat}}) => {
  const errors = [];

  if (!(await isGitRepo({cwd, env}))) {
@@ -24,14 +24,6 @@ module.exports = async ({cwd, env, options: {repositoryUrl, tagFormat, branches}
    errors.push(getError('ETAGNOVERSION', {tagFormat}));
  }

-  branches.forEach(branch => {
-    if (
-      !((isString(branch) && branch.trim()) || (isPlainObject(branch) && isString(branch.name) && branch.name.trim()))
-    ) {
-      errors.push(getError('EINVALIDBRANCH', {branch}));
-    }
-  });
-
  if (errors.length > 0) {
    throw new AggregateError(errors);
  }
@@ -3,6 +3,14 @@
  "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"
  },
@@ -19,56 +27,54 @@
    "Pierre Vanduynslager (https://twitter.com/@pvdlg_)"
  ],
  "dependencies": {
-    "@semantic-release/commit-analyzer": "^7.0.0-beta.2",
+    "@semantic-release/commit-analyzer": "^6.1.0",
    "@semantic-release/error": "^2.2.0",
-    "@semantic-release/github": "^5.3.0-beta.1",
-    "@semantic-release/npm": "^5.2.0-beta.1",
+    "@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",
+    "hook-std": "^2.0.0",
    "hosted-git-info": "^2.7.1",
-    "lodash": "^4.17.4",
-    "marked": "^0.5.0",
-    "marked-terminal": "^3.0.0",
-    "micromatch": "3.1.5",
-    "p-each-series": "^1.0.0",
-    "p-reduce": "^1.0.0",
-    "read-pkg-up": "^4.0.0",
-    "resolve-from": "^4.0.0",
-    "semver": "^5.4.1",
-    "semver-diff": "^2.1.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": "^6.0.0",
+    "resolve-from": "^5.0.0",
+    "semver": "^6.0.0",
    "signale": "^1.2.1",
-    "yargs": "^12.0.0"
+    "yargs": "^13.1.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",
+    "commitizen": "^4.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",
+    "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": "^13.1.0",
-    "p-retry": "^3.0.0",
+    "nyc": "^14.0.0",
+    "p-retry": "^4.0.0",
    "proxyquire": "^2.0.0",
-    "sinon": "^7.1.1",
+    "sinon": "^7.2.7",
    "stream-buffers": "^3.0.2",
-    "tempy": "^0.2.1",
-    "xo": "^0.23.0"
+    "tempy": "^0.3.0",
+    "xo": "^0.24.0"
  },
  "engines": {
    "node": ">=8.3"
@@ -112,7 +118,7 @@
    "trailingComma": "es5"
  },
  "publishConfig": {
-    "access": "public"
+    "tag": "next"
  },
  "repository": {
    "type": "git",
@@ -1,199 +0,0 @@
-import test from 'ava';
-import {union} from 'lodash';
-import semver from 'semver';
-import proxyquire from 'proxyquire';
-
-const getBranch = (branches, branch) => branches.find(({name}) => name === branch);
-const release = (branches, name, version) => getBranch(branches, name).tags.push({version});
-const merge = (branches, source, target, tag) => {
-  getBranch(branches, target).tags = union(
-    getBranch(branches, source).tags.filter(({version}) => !tag || semver.cmp(version, '<=', tag)),
-    getBranch(branches, target).tags
-  );
-};
-
-test('Enforce ranges with branching release workflow', async t => {
-  const branches = [
-    {name: '1.x', tags: []},
-    {name: '1.0.x', tags: []},
-    {name: 'master', tags: []},
-    {name: 'next', tags: []},
-    {name: 'next-major', tags: []},
-    {name: 'beta', prerelease: true, tags: []},
-    {name: 'alpha', prerelease: true, tags: []},
-  ];
-  const getBranches = proxyquire('../../lib/branches', {'./get-tags': () => branches, './expand': () => []});
-
-  let result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, '1.0.x').range, '>=1.0.0 <1.0.0', 'Cannot release on 1.0.x before a releasing on master');
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.0.0', 'Cannot release on 1.x before a releasing on master');
-  t.is(getBranch(result, 'master').range, '>=1.0.0 <1.1.0', 'Can release only patch on master');
-  t.is(getBranch(result, 'next').range, '>=1.1.0 <2.0.0', 'Can release only minor on next');
-  t.is(getBranch(result, 'next-major').range, '>=2.0.0', 'Can release only major on next-major');
-
-  release(branches, 'master', '1.0.0');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, '1.0.x').range, '>=1.0.0 <1.0.0', 'Cannot release on 1.0.x before a releasing on master');
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.0.0', 'Cannot release on 1.x before a releasing on master');
-  t.is(getBranch(result, 'master').range, '>=1.0.0 <1.1.0', 'Can release only patch on master');
-
-  release(branches, 'master', '1.0.1');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.0.1 <1.1.0', 'Can release only patch, > than 1.0.1 on master');
-
-  merge(branches, 'master', 'next');
-  merge(branches, 'master', 'next-major');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.0.1 <1.1.0', 'Can release only patch, > than 1.0.1 on master');
-  t.is(getBranch(result, 'next').range, '>=1.1.0 <2.0.0', 'Can release only minor on next');
-  t.is(getBranch(result, 'next-major').range, '>=2.0.0', 'Can release only major on next-major');
-
-  release(branches, 'next', '1.1.0');
-  release(branches, 'next', '1.1.1');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'next').range, '>=1.1.1 <2.0.0', 'Can release only patch or minor, > than 1.1.0 on next');
-
-  release(branches, 'next-major', '2.0.0');
-  release(branches, 'next-major', '2.0.1');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'next-major').range, '>=2.0.1', 'Can release any version, > than 2.0.1 on next-major');
-
-  merge(branches, 'next-major', 'beta');
-  release(branches, 'beta', '3.0.0-beta.1');
-  merge(branches, 'beta', 'alpha');
-  release(branches, 'alpha', '4.0.0-alpha.1');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'next-major').range, '>=2.0.1', 'Can release any version, > than 2.0.1 on next-major');
-
-  merge(branches, 'master', '1.0.x');
-  merge(branches, 'master', '1.x');
-  release(branches, 'master', '1.0.1');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.0.1 <1.1.0', 'Can release only patch, > than 1.0.1 on master');
-  t.is(
-    getBranch(result, '1.0.x').range,
-    '>=1.0.1 <1.0.1',
-    'Cannot release on 1.0.x before >= 1.1.0 is released on master'
-  );
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.0.1', 'Cannot release on 1.x before >= 1.2.0 is released on master');
-
-  release(branches, 'master', '1.0.2');
-  release(branches, 'master', '1.0.3');
-  release(branches, 'master', '1.0.4');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.0.4 <1.1.0', 'Can release only patch, > than 1.0.4 on master');
-  t.is(
-    getBranch(result, '1.0.x').range,
-    '>=1.0.1 <1.0.2',
-    'Cannot release on 1.0.x before >= 1.1.0 is released on master'
-  );
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.0.2', 'Cannot release on 1.x before >= 1.2.0 is released on master');
-
-  merge(branches, 'next', 'master');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.1.1 <1.2.0', 'Can release only patch, > than 1.1.1 on master');
-  t.is(getBranch(result, 'next').range, '>=1.2.0 <2.0.0', 'Can release only patch or minor, > than 1.2.0 on next');
-  t.is(getBranch(result, 'next-major').range, '>=2.0.1', 'Can release any version, > than 2.0.1 on next-major');
-  t.is(
-    getBranch(result, '1.0.x').range,
-    '>=1.0.1 <1.0.2',
-    'Cannot release on 1.0.x before 1.0.x version from master are merged'
-  );
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.0.2', 'Cannot release on 1.x before >= 2.0.0 is released on master');
-
-  merge(branches, 'master', '1.0.x', '1.0.4');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.1.1 <1.2.0', 'Can release only patch, > than 1.1.1 on master');
-  t.is(getBranch(result, '1.0.x').range, '>=1.0.4 <1.1.0', 'Can release on 1.0.x only within range');
-  t.is(getBranch(result, '1.x').range, '>=1.1.0 <1.1.0', 'Cannot release on 1.x before >= 2.0.0 is released on master');
-
-  merge(branches, 'master', '1.x');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=1.1.1 <1.2.0', 'Can release only patch, > than 1.1.1 on master');
-  t.is(getBranch(result, '1.0.x').range, '>=1.0.4 <1.1.0', 'Can release on 1.0.x only within range');
-  t.is(getBranch(result, '1.x').range, '>=1.1.1 <1.1.1', 'Cannot release on 1.x before >= 2.0.0 is released on master');
-
-  merge(branches, 'next-major', 'next');
-  merge(branches, 'next', 'master');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=2.0.1 <2.1.0', 'Can release only patch, > than 2.0.1 on master');
-  t.is(getBranch(result, 'next').range, '>=2.1.0 <3.0.0', 'Can release only minor on next');
-  t.is(getBranch(result, 'next-major').range, '>=3.0.0', 'Can release only major on next-major');
-  t.is(getBranch(result, '1.x').range, '>=1.1.1 <2.0.0', 'Can release on 1.x only within range');
-
-  merge(branches, 'beta', 'master');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, 'master').range, '>=2.0.1 <2.1.0', 'Can release only patch, > than 2.0.1 on master');
-  t.is(getBranch(result, 'next').range, '>=2.1.0 <3.0.0', 'Can release only minor on next');
-  t.is(getBranch(result, 'next-major').range, '>=3.0.0', 'Can release only major on next-major');
-
-  branches.push({name: '1.1.x', tags: []});
-  merge(branches, '1.x', '1.1.x');
-  result = (await getBranches({options: {branches}})).map(({name, range}) => ({name, range}));
-  t.is(getBranch(result, '1.0.x').range, '>=1.0.4 <1.1.0', 'Can release on 1.0.x only within range');
-  t.is(getBranch(result, '1.1.x').range, '>=1.1.1 <1.2.0', 'Can release on 1.1.x only within range');
-  t.is(getBranch(result, '1.x').range, '>=1.2.0 <2.0.0', 'Can release on 1.x only within range');
-});
-
-test('Throw SemanticReleaseError for invalid configurations', async t => {
-  const branches = [
-    {name: '123', range: '123', tags: []},
-    {name: '1.x', tags: []},
-    {name: 'maintenance-1', range: '1.x', tags: []},
-    {name: '1.x.x', tags: []},
-    {name: 'beta', prerelease: '', tags: []},
-    {name: 'alpha', prerelease: 'alpha', tags: []},
-    {name: 'preview', prerelease: 'alpha', tags: []},
-  ];
-  const getBranches = proxyquire('../../lib/branches', {'./get-tags': () => branches, './expand': () => []});
-  const errors = [...(await t.throws(getBranches({options: {branches}})))];
-
-  t.is(errors[0].name, 'SemanticReleaseError');
-  t.is(errors[0].code, 'EMAINTENANCEBRANCH');
-  t.truthy(errors[0].message);
-  t.truthy(errors[0].details);
-  t.is(errors[1].name, 'SemanticReleaseError');
-  t.is(errors[1].code, 'EMAINTENANCEBRANCHES');
-  t.truthy(errors[1].message);
-  t.truthy(errors[1].details);
-  t.is(errors[2].name, 'SemanticReleaseError');
-  t.is(errors[2].code, 'EPRERELEASEBRANCH');
-  t.truthy(errors[2].message);
-  t.truthy(errors[2].details);
-  t.is(errors[3].name, 'SemanticReleaseError');
-  t.is(errors[3].code, 'EPRERELEASEBRANCHES');
-  t.truthy(errors[3].message);
-  t.truthy(errors[3].details);
-  t.is(errors[4].name, 'SemanticReleaseError');
-  t.is(errors[4].code, 'ERELEASEBRANCHES');
-  t.truthy(errors[4].message);
-  t.truthy(errors[4].details);
-});
-
-test('Throw a SemanticReleaseError if there is duplicate branches', async t => {
-  const branches = [{name: 'master', tags: []}, {name: 'master', tags: []}];
-  const getBranches = proxyquire('../../lib/branches', {'./get-tags': () => branches, './expand': () => []});
-
-  const errors = [...(await t.throws(getBranches({options: {branches}})))];
-
-  t.is(errors[0].name, 'SemanticReleaseError');
-  t.is(errors[0].code, 'EDUPLICATEBRANCHES');
-  t.truthy(errors[0].message);
-  t.truthy(errors[0].details);
-});
-
-test('Throw a SemanticReleaseError for each invalid branch name', async t => {
-  const branches = [{name: '~master', tags: []}, {name: '^master', tags: []}];
-  const getBranches = proxyquire('../../lib/branches', {'./get-tags': () => branches, './expand': () => []});
-
-  const errors = [...(await t.throws(getBranches({options: {branches}})))];
-
-  t.is(errors[0].name, 'SemanticReleaseError');
-  t.is(errors[0].code, 'EINVALIDBRANCHNAME');
-  t.truthy(errors[0].message);
-  t.truthy(errors[0].details);
-  t.is(errors[1].name, 'SemanticReleaseError');
-  t.is(errors[1].code, 'EINVALIDBRANCHNAME');
-  t.truthy(errors[1].message);
-  t.truthy(errors[1].details);
-});
@@ -1,54 +0,0 @@
-import test from 'ava';
-import expand from '../../lib/branches/expand';
-import {gitRepo, gitCommits, gitCheckout, gitPush} from '../helpers/git-utils';
-
-test('Expand branches defined with globs', async t => {
-  const {cwd, repositoryUrl} = await gitRepo(true);
-  await gitCommits(['First'], {cwd});
-  await gitPush(repositoryUrl, 'master', {cwd});
-  await gitCheckout('1.1.x', true, {cwd});
-  await gitCommits(['Second'], {cwd});
-  await gitPush(repositoryUrl, '1.1.x', {cwd});
-  await gitCheckout('1.x.x', true, {cwd});
-  await gitCommits(['Third'], {cwd});
-  await gitPush(repositoryUrl, '1.x.x', {cwd});
-  await gitCheckout('2.x', true, {cwd});
-  await gitCommits(['Fourth'], {cwd});
-  await gitPush(repositoryUrl, '2.x', {cwd});
-  await gitCheckout('next', true, {cwd});
-  await gitCommits(['Fifth'], {cwd});
-  await gitPush(repositoryUrl, 'next', {cwd});
-  await gitCheckout('pre/foo', true, {cwd});
-  await gitCommits(['Sixth'], {cwd});
-  await gitPush(repositoryUrl, 'pre/foo', {cwd});
-  await gitCheckout('pre/bar', true, {cwd});
-  await gitCommits(['Seventh'], {cwd});
-  await gitPush(repositoryUrl, 'pre/bar', {cwd});
-  await gitCheckout('beta', true, {cwd});
-  await gitCommits(['Eighth'], {cwd});
-  await gitPush(repositoryUrl, 'beta', {cwd});
-
-  const branches = [
-    // Should match all maintenance type branches
-    {name: '+([1-9])?(.{+([1-9]),x}).x'},
-    {name: 'master', channel: 'latest'},
-    {name: 'next'},
-    {name: 'pre/{foo,bar}', channel: `\${name.replace(/^pre\\//g, '')}`, prerelease: true},
-    // Should be ignored as there is no matching branches in the repo
-    {name: 'missing'},
-    // Should be ignored as the matching branch in the repo is already matched by `/^pre\\/(\\w+)$/gi`
-    {name: '*/foo', channel: 'foo', prerelease: 'foo'},
-    {name: 'beta', channel: `channel-\${name}`, prerelease: true},
-  ];
-
-  t.deepEqual(await expand({cwd}, branches), [
-    {name: '1.1.x'},
-    {name: '1.x.x'},
-    {name: '2.x'},
-    {name: 'master', channel: 'latest'},
-    {name: 'next'},
-    {name: 'pre/bar', channel: 'bar', prerelease: true},
-    {name: 'pre/foo', channel: 'foo', prerelease: true},
-    {name: 'beta', channel: 'channel-beta', prerelease: true},
-  ]);
-});
@@ -1,202 +0,0 @@
-import test from 'ava';
-import getTags from '../../lib/branches/get-tags';
-import {gitRepo, gitCommits, gitTagVersion, gitCheckout, merge, changeAuthor} from '../helpers/git-utils';
-
-test('Get the valid tags', async t => {
-  const {cwd} = await gitRepo();
-  const commits = await gitCommits(['First'], {cwd});
-  await gitTagVersion('foo', undefined, {cwd});
-  await gitTagVersion('v2.0.0', undefined, {cwd});
-  commits.push(...(await gitCommits(['Second'], {cwd})));
-  await gitTagVersion('v1.0.0', undefined, {cwd});
-  commits.push(...(await gitCommits(['Third'], {cwd})));
-  await gitTagVersion('v3.0', undefined, {cwd});
-  commits.push(...(await gitCommits(['Fourth'], {cwd})));
-  await gitTagVersion('v3.0.0-beta.1', undefined, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `v\${version}`}}, [{name: 'master'}]);
-
-  t.deepEqual(result, [
-    {
-      name: 'master',
-      tags: [
-        {gitTag: 'v1.0.0', version: '1.0.0', channel: undefined, gitHead: commits[1].hash},
-        {gitTag: 'v2.0.0', version: '2.0.0', channel: undefined, gitHead: commits[0].hash},
-        {gitTag: 'v3.0.0-beta.1', version: '3.0.0-beta.1', channel: undefined, gitHead: commits[3].hash},
-      ],
-    },
-  ]);
-});
-
-test('Get the valid tags from multiple branches', async t => {
-  const {cwd} = await gitRepo();
-  const commits = await gitCommits(['First'], {cwd});
-  await gitTagVersion('v1.0.0', undefined, {cwd});
-  await gitTagVersion('v1.0.0@1.x', undefined, {cwd});
-  commits.push(...(await gitCommits(['Second'], {cwd})));
-  await gitTagVersion('v1.1.0', undefined, {cwd});
-  await gitTagVersion('v1.1.0@1.x', undefined, {cwd});
-  await gitCheckout('1.x', true, {cwd});
-  await gitCheckout('master', false, {cwd});
-  commits.push(...(await gitCommits(['Third'], {cwd})));
-  await gitTagVersion('v2.0.0', undefined, {cwd});
-  await gitTagVersion('v2.0.0@next', undefined, {cwd});
-  await gitCheckout('next', true, {cwd});
-  commits.push(...(await gitCommits(['Fourth'], {cwd})));
-  await gitTagVersion('v3.0.0@next', undefined, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `v\${version}`}}, [
-    {name: '1.x'},
-    {name: 'master'},
-    {name: 'next'},
-  ]);
-
-  t.deepEqual(result, [
-    {
-      name: '1.x',
-      tags: [
-        {gitTag: 'v1.0.0', version: '1.0.0', channel: undefined, gitHead: commits[0].hash},
-        {gitTag: 'v1.0.0@1.x', version: '1.0.0', channel: '1.x', gitHead: commits[0].hash},
-        {gitTag: 'v1.1.0', version: '1.1.0', channel: undefined, gitHead: commits[1].hash},
-        {gitTag: 'v1.1.0@1.x', version: '1.1.0', channel: '1.x', gitHead: commits[1].hash},
-      ],
-    },
-    {
-      name: 'master',
-      tags: [
-        ...result[0].tags,
-        {gitTag: 'v2.0.0', version: '2.0.0', channel: undefined, gitHead: commits[2].hash},
-        {gitTag: 'v2.0.0@next', version: '2.0.0', channel: 'next', gitHead: commits[2].hash},
-      ],
-    },
-    {
-      name: 'next',
-      tags: [...result[1].tags, {gitTag: 'v3.0.0@next', version: '3.0.0', channel: 'next', gitHead: commits[3].hash}],
-    },
-  ]);
-});
-
-test('Match the tag name from the begining of the string and the channel from the last "@"', async t => {
-  const {cwd} = await gitRepo();
-  const commits = await gitCommits(['First'], {cwd});
-  await gitTagVersion('prefix@v1.0.0', undefined, {cwd});
-  await gitTagVersion('prefix@v1.0.0@next', undefined, {cwd});
-  await gitTagVersion('prefix@v2.0.0', undefined, {cwd});
-  await gitTagVersion('prefix@v2.0.0@next', undefined, {cwd});
-  await gitTagVersion('other-prefix@v3.0.0', undefined, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `prefix@v\${version}`}}, [{name: 'master'}]);
-
-  t.deepEqual(result, [
-    {
-      name: 'master',
-      tags: [
-        {gitTag: 'prefix@v1.0.0', version: '1.0.0', channel: undefined, gitHead: commits[0].hash},
-        {gitTag: 'prefix@v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: commits[0].hash},
-        {gitTag: 'prefix@v2.0.0', version: '2.0.0', channel: undefined, gitHead: commits[0].hash},
-        {gitTag: 'prefix@v2.0.0@next', version: '2.0.0', channel: 'next', gitHead: commits[0].hash},
-      ],
-    },
-  ]);
-});
-
-test('Return branches with and empty tags array if no valid tag is found', async t => {
-  const {cwd} = await gitRepo();
-  await gitCommits(['First'], {cwd});
-  await gitTagVersion('foo', undefined, {cwd});
-  await gitCommits(['Second'], {cwd});
-  await gitTagVersion('v2.0.x', undefined, {cwd});
-  await gitCommits(['Third'], {cwd});
-  await gitTagVersion('v3.0', undefined, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `prefix@v\${version}`}}, [{name: 'master'}, {name: 'next'}]);
-
-  t.deepEqual(result, [{name: 'master', tags: []}, {name: 'next', tags: []}]);
-});
-
-test('Return branches with and empty tags array if no valid tag is found in history of configured branches', async t => {
-  const {cwd} = await gitRepo();
-  await gitCommits(['First'], {cwd});
-  await gitCheckout('other-branch', true, {cwd});
-  await gitCommits(['Second'], {cwd});
-  await gitTagVersion('v1.0.0', undefined, {cwd});
-  await gitTagVersion('v1.0.0@next', undefined, {cwd});
-  await gitTagVersion('v2.0.0', undefined, {cwd});
-  await gitTagVersion('v2.0.0@next', undefined, {cwd});
-  await gitTagVersion('v3.0.0', undefined, {cwd});
-  await gitTagVersion('v3.0.0@next', undefined, {cwd});
-  await gitCheckout('master', false, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `prefix@v\${version}`}}, [{name: 'master'}, {name: 'next'}]);
-
-  t.deepEqual(result, [{name: 'master', tags: []}, {name: 'next', tags: []}]);
-});
-
-test('Get the highest valid tag corresponding to the "tagFormat"', async t => {
-  const {cwd} = await gitRepo();
-  const commits = await gitCommits(['First'], {cwd});
-
-  await gitTagVersion('1.0.0', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `\${version}`}}, [{name: 'master'}]), [
-    {name: 'master', tags: [{gitTag: '1.0.0', version: '1.0.0', channel: undefined, gitHead: commits[0].hash}]},
-  ]);
-
-  await gitTagVersion('foo-1.0.0-bar', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `foo-\${version}-bar`}}, [{name: 'master'}]), [
-    {name: 'master', tags: [{gitTag: 'foo-1.0.0-bar', version: '1.0.0', channel: undefined, gitHead: commits[0].hash}]},
-  ]);
-
-  await gitTagVersion('foo-v1.0.0-bar', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `foo-v\${version}-bar`}}, [{name: 'master'}]), [
-    {
-      name: 'master',
-      tags: [{gitTag: 'foo-v1.0.0-bar', version: '1.0.0', channel: undefined, gitHead: commits[0].hash}],
-    },
-  ]);
-
-  await gitTagVersion('(.+)/1.0.0/(a-z)', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `(.+)/\${version}/(a-z)`}}, [{name: 'master'}]), [
-    {
-      name: 'master',
-      tags: [{gitTag: '(.+)/1.0.0/(a-z)', version: '1.0.0', channel: undefined, gitHead: commits[0].hash}],
-    },
-  ]);
-
-  await gitTagVersion('2.0.0-1.0.0-bar.1', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `2.0.0-\${version}-bar.1`}}, [{name: 'master'}]), [
-    {
-      name: 'master',
-      tags: [{gitTag: '2.0.0-1.0.0-bar.1', version: '1.0.0', channel: undefined, gitHead: commits[0].hash}],
-    },
-  ]);
-
-  await gitTagVersion('3.0.0-bar.2', undefined, {cwd});
-  t.deepEqual(await getTags({cwd, options: {tagFormat: `\${version}-bar.2`}}, [{name: 'master'}]), [
-    {name: 'master', tags: [{gitTag: '3.0.0-bar.2', version: '3.0.0', channel: undefined, gitHead: commits[0].hash}]},
-  ]);
-});
-
-test('Get the tag on branch where commits have been rebased', async t => {
-  const {cwd} = await gitRepo();
-  const commits = await gitCommits(['First'], {cwd});
-  await gitCheckout('next', true, {cwd});
-  commits.push(...(await gitCommits(['Second/n/n/commit body'], {cwd})));
-  await gitTagVersion('v1.0.0@next', undefined, {cwd});
-  await gitCheckout('master', false, {cwd});
-  await merge('next', {cwd});
-  // Simulate GitHub "Rebase and Merge" by changing the committer info, which will result in a new commit sha and losing the tag
-  await changeAuthor(commits[1].hash, {cwd});
-
-  const result = await getTags({cwd, options: {tagFormat: `v\${version}`}}, [{name: 'master'}, {name: 'next'}]);
-
-  t.deepEqual(result, [
-    {
-      name: 'master',
-      tags: [{gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: commits[1].hash}],
-    },
-    {
-      name: 'next',
-      tags: [{gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: commits[1].hash}],
-    },
-  ]);
-});
@@ -1,307 +0,0 @@
-import test from 'ava';
-import normalize from '../../lib/branches/normalize';
-
-const toTags = versions => versions.map(version => ({version}));
-
-test('Maintenance branches - initial state', t => {
-  const maintenance = [{name: '1.x', tags: []}, {name: '1.1.x', tags: []}, {name: '1.2.x', tags: []}];
-  const release = [{name: 'master', tags: []}];
-  t.deepEqual(
-    normalize
-      .maintenance({maintenance, release})
-      .map(({type, name, range, accept, channel, 'merge-range': maintenanceRange}) => ({
-        type,
-        name,
-        range,
-        accept,
-        channel,
-        'merge-range': maintenanceRange,
-      })),
-    [
-      {
-        type: 'maintenance',
-        name: '1.1.x',
-        range: '>=1.1.0 <1.0.0',
-        accept: [],
-        channel: '1.1.x',
-        'merge-range': '>=1.1.0 <1.2.0',
-      },
-      {
-        type: 'maintenance',
-        name: '1.2.x',
-        range: '>=1.2.0 <1.0.0',
-        accept: [],
-        channel: '1.2.x',
-        'merge-range': '>=1.2.0 <1.3.0',
-      },
-      {
-        type: 'maintenance',
-        name: '1.x',
-        range: '>=1.3.0 <1.0.0',
-        accept: [],
-        channel: '1.x',
-        'merge-range': '>=1.3.0 <2.0.0',
-      },
-    ]
-  );
-});
-
-test('Maintenance branches - cap range to first release present on default branch and not in any Maintenance one', t => {
-  const maintenance = [
-    {name: '1.x', tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0', '1.2.1', '1.3.0', '1.4.0', '1.5.0'])},
-    {name: 'name', range: '1.1.x', tags: toTags(['1.0.0', '1.0.1', '1.1.0', '1.1.1'])},
-    {name: '1.2.x', tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0', '1.2.1'])},
-    {name: '2.x.x', tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0', '1.2.1', '1.5.0'])},
-  ];
-  const release = [
-    {
-      name: 'master',
-      tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0', '1.2.1', '1.3.0', '1.4.0', '1.5.0', '1.6.0', '2.0.0']),
-    },
-  ];
-
-  t.deepEqual(
-    normalize
-      .maintenance({maintenance, release})
-      .map(({type, name, range, accept, channel, 'merge-range': maintenanceRange}) => ({
-        type,
-        name,
-        range,
-        accept,
-        channel,
-        'merge-range': maintenanceRange,
-      })),
-    [
-      {
-        type: 'maintenance',
-        name: 'name',
-        range: '>=1.1.1 <1.2.0',
-        accept: ['patch'],
-        channel: 'name',
-        'merge-range': '>=1.1.0 <1.2.0',
-      },
-      {
-        type: 'maintenance',
-        name: '1.2.x',
-        range: '>=1.2.1 <1.3.0',
-        accept: ['patch'],
-        channel: '1.2.x',
-        'merge-range': '>=1.2.0 <1.3.0',
-      },
-      {
-        type: 'maintenance',
-        name: '1.x',
-        range: '>=1.5.0 <1.6.0',
-        accept: ['patch'],
-        channel: '1.x',
-        'merge-range': '>=1.3.0 <2.0.0',
-      },
-      {
-        type: 'maintenance',
-        name: '2.x.x',
-        range: '>=2.0.0 <1.6.0',
-        accept: [],
-        channel: '2.x.x',
-        'merge-range': '>=2.0.0 <3.0.0',
-      },
-    ]
-  );
-});
-
-test('Maintenance branches - cap range to default branch last release if all release are also present on maintenance branch', t => {
-  const maintenance = [
-    {name: '1.x', tags: toTags(['1.0.0', '1.2.0', '1.3.0'])},
-    {name: '2.x.x', tags: toTags(['1.0.0', '1.2.0', '1.3.0', '2.0.0'])},
-  ];
-  const release = [{name: 'master', tags: toTags(['1.0.0', '1.2.0', '1.3.0', '2.0.0'])}];
-
-  t.deepEqual(
-    normalize
-      .maintenance({maintenance, release})
-      .map(({type, name, range, accept, channel, 'merge-range': maintenanceRange}) => ({
-        type,
-        name,
-        range,
-        accept,
-        channel,
-        'merge-range': maintenanceRange,
-      })),
-    [
-      {
-        type: 'maintenance',
-        name: '1.x',
-        range: '>=1.3.0 <2.0.0',
-        accept: ['patch', 'minor'],
-        channel: '1.x',
-        'merge-range': '>=1.0.0 <2.0.0',
-      },
-      {
-        type: 'maintenance',
-        name: '2.x.x',
-        range: '>=2.0.0 <2.0.0',
-        accept: [],
-        channel: '2.x.x',
-        'merge-range': '>=2.0.0 <3.0.0',
-      },
-    ]
-  );
-});
-
-test('Release branches - initial state', t => {
-  const release = [{name: 'master', tags: []}, {name: 'next', tags: []}, {name: 'next-major', tags: []}];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=1.0.0 <1.1.0', accept: ['patch'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=1.1.0 <2.0.0', accept: ['patch', 'minor'], channel: 'next'},
-      {
-        type: 'release',
-        name: 'next-major',
-        range: '>=2.0.0',
-        accept: ['patch', 'minor', 'major'],
-        channel: 'next-major',
-      },
-    ]
-  );
-});
-
-test('Release branches - 3 release branches', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '1.0.1', '1.0.2'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.0.1', '1.0.2', '1.1.0', '1.2.0'])},
-    {name: 'next-major', tags: toTags(['1.0.0', '1.0.1', '1.0.2', '1.1.0', '1.2.0', '2.0.0', '2.0.1', '2.1.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=1.0.2 <1.1.0', accept: ['patch'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=1.2.0 <2.0.0', accept: ['patch', 'minor'], channel: 'next'},
-      {
-        type: 'release',
-        name: 'next-major',
-        range: '>=2.1.0',
-        accept: ['patch', 'minor', 'major'],
-        channel: 'next-major',
-      },
-    ]
-  );
-});
-
-test('Release branches - 2 release branches', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '1.0.1', '1.1.0', '1.1.1', '1.2.0'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.0.1', '1.1.0', '1.1.1', '1.2.0', '2.0.0', '2.0.1', '2.1.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=1.2.0 <2.0.0', accept: ['patch', 'minor'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=2.1.0', accept: ['patch', 'minor', 'major'], channel: 'next'},
-    ]
-  );
-});
-
-test('Release branches - 1 release branches', t => {
-  const release = [{name: 'master', tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0'])}];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [{type: 'release', name: 'master', range: '>=1.2.0', accept: ['patch', 'minor', 'major'], channel: undefined}]
-  );
-});
-
-test('Release branches - cap ranges to first release only present on following branch', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '1.1.0', '1.2.0', '2.0.0'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.1.0', '1.2.0', '2.0.0', '2.1.0'])},
-    {name: 'next-major', tags: toTags(['1.0.0', '1.1.0', '1.2.0', '2.0.0', '2.1.0', '2.2.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=2.0.0 <2.1.0', accept: ['patch'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=2.1.0 <2.2.0', accept: ['patch'], channel: 'next'},
-      {
-        type: 'release',
-        name: 'next-major',
-        range: '>=2.2.0',
-        accept: ['patch', 'minor', 'major'],
-        channel: 'next-major',
-      },
-    ]
-  );
-});
-
-test('Release branches - Handle missing previous tags in branch history', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '2.0.0'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.1.0', '1.1.1', '1.2.0', '2.0.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=2.0.0 <3.0.0', accept: ['patch', 'minor'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=3.0.0', accept: ['patch', 'minor', 'major'], channel: 'next'},
-    ]
-  );
-});
-
-test('Release branches - enforce release gaps after downstream merge', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '1.1.0', '2.0.0'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.1.0', '2.0.0'])},
-    {name: 'next-major', tags: toTags(['1.0.0', '1.1.0', '2.0.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=2.0.0 <2.1.0', accept: ['patch'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=2.1.0 <3.0.0', accept: ['patch', 'minor'], channel: 'next'},
-      {
-        type: 'release',
-        name: 'next-major',
-        range: '>=3.0.0',
-        accept: ['patch', 'minor', 'major'],
-        channel: 'next-major',
-      },
-    ]
-  );
-});
-
-test('Release branches - limit releases on 2nd and 3rd branche based on 1st branch last release', t => {
-  const release = [
-    {name: 'master', tags: toTags(['1.0.0', '1.1.0', '2.0.0', '3.0.0'])},
-    {name: 'next', tags: toTags(['1.0.0', '1.1.0'])},
-    {name: 'next-major', tags: toTags(['1.0.0', '1.1.0', '2.0.0'])},
-  ];
-
-  t.deepEqual(
-    normalize.release({release}).map(({type, name, range, accept, channel}) => ({type, name, range, accept, channel})),
-    [
-      {type: 'release', name: 'master', range: '>=3.0.0 <3.1.0', accept: ['patch'], channel: undefined},
-      {type: 'release', name: 'next', range: '>=3.1.0 <4.0.0', accept: ['patch', 'minor'], channel: 'next'},
-      {
-        type: 'release',
-        name: 'next-major',
-        range: '>=4.0.0',
-        accept: ['patch', 'minor', 'major'],
-        channel: 'next-major',
-      },
-    ]
-  );
-});
-
-test('Prerelease branches', t => {
-  const prerelease = [{name: 'beta', prerelease: true, tags: []}, {name: 'alpha', prerelease: 'preview', tags: []}];
-
-  t.deepEqual(normalize.prerelease({prerelease}).map(({type, name, channel}) => ({type, name, channel})), [
-    {type: 'prerelease', name: 'beta', channel: 'beta'},
-    {type: 'prerelease', name: 'alpha', channel: 'alpha'},
-  ]);
-});
@@ -29,7 +29,6 @@ test.serial('Pass options to semantic-release API', async t => {
    '',
    '-b',
    'master',
-    'next',
    '-r',
    'https://github/com/owner/repo.git',
    '-t',
@@ -67,9 +66,9 @@ 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.deepEqual(run.args[0][0].branches, ['master', 'next']);
+  t.is(run.args[0][0].branch, 'master');
  t.is(run.args[0][0].repositoryUrl, 'https://github/com/owner/repo.git');
  t.is(run.args[0][0].tagFormat, `v\${version}`);
  t.deepEqual(run.args[0][0].plugins, ['plugin1', 'plugin2']);
@@ -85,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 => {
@@ -93,7 +92,7 @@ test.serial('Pass options to semantic-release API with alias arguments', async t
  const argv = [
    '',
    '',
-    '--branches',
+    '--branch',
    'master',
    '--repository-url',
    'https://github/com/owner/repo.git',
@@ -109,16 +108,16 @@ 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.deepEqual(run.args[0][0].branches, ['master']);
+  t.is(run.args[0][0].branch, 'master');
  t.is(run.args[0][0].repositoryUrl, 'https://github/com/owner/repo.git');
  t.is(run.args[0][0].tagFormat, `v\${version}`);
  t.deepEqual(run.args[0][0].plugins, ['plugin1', 'plugin2']);
  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 => {
@@ -126,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 => {
@@ -140,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 => {
@@ -169,10 +168,10 @@ test.serial('Display help', async t => {
  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 => {
@@ -180,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 => {
@@ -192,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 => {
@@ -204,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 => {
@@ -216,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);
 });
@@ -1,86 +0,0 @@
-import test from 'ava';
-import {maintenance, prerelease, release} from '../../lib/definitions/branches';
-
-test('A "maintenance" branch is identified by having a "range" property or a "name" formatted like "N.x", "N.x.x" or "N.N.x"', t => {
-  t.true(maintenance.filter({name: '1.x.x'}));
-  t.true(maintenance.filter({name: '1.0.x'}));
-  t.true(maintenance.filter({name: '1.x'}));
-  t.true(maintenance.filter({name: 'some-name', range: '1.x.x'}));
-  t.true(maintenance.filter({name: 'some-name', range: '1.1.x'}));
-  t.true(maintenance.filter({name: 'some-name', range: ''}));
-  t.true(maintenance.filter({name: 'some-name', range: null}));
-  t.true(maintenance.filter({name: 'some-name', range: false}));
-
-  t.false(maintenance.filter({name: 'some-name'}));
-  t.false(maintenance.filter({name: '1.0.0'}));
-  t.false(maintenance.filter({name: 'x.x.x'}));
-});
-
-test('A "maintenance" branches must have a "range" property formatted like "N.x", "N.x.x" or "N.N.x"', t => {
-  t.true(maintenance.branchValidator({name: 'some-name', range: '1.x.x'}));
-  t.true(maintenance.branchValidator({name: 'some-name', range: '1.1.x'}));
-
-  t.false(maintenance.branchValidator({name: 'some-name', range: '^1.0.0'}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: '>=1.0.0 <2.0.0'}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: '1.0.0'}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: 'wrong-range'}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: ''}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: null}));
-  t.false(maintenance.branchValidator({name: 'some-name', range: false}));
-});
-
-test('The "maintenance" branches must have unique ranges', t => {
-  t.true(maintenance.branchesValidator([{range: '1.x.x'}, {range: '1.0.x'}]));
-
-  t.false(maintenance.branchesValidator([{range: '1.x.x'}, {range: '1.x.x'}]));
-  t.false(maintenance.branchesValidator([{range: '1.x.x'}, {range: '1.x'}]));
-});
-
-test('A "prerelease" branch is identified by having a range "prerelease" property', t => {
-  t.true(prerelease.filter({name: 'some-name', prerelease: true}));
-  t.true(prerelease.filter({name: 'some-name', prerelease: 'beta'}));
-  t.true(prerelease.filter({name: 'some-name', prerelease: ''}));
-  t.true(prerelease.filter({name: 'some-name', prerelease: null}));
-  t.true(prerelease.filter({name: 'some-name', prerelease: false}));
-
-  t.false(prerelease.filter({name: 'some-name'}));
-});
-
-test('A "prerelease" branch must have a valid prerelease detonation in "prerelease" property or in "name" if "prerelease" is "true"', t => {
-  t.true(prerelease.branchValidator({name: 'beta', prerelease: true}));
-  t.true(prerelease.branchValidator({name: 'some-name', prerelease: 'beta'}));
-
-  t.false(prerelease.branchValidator({name: 'some-name', prerelease: ''}));
-  t.false(prerelease.branchValidator({name: 'some-name', prerelease: null}));
-  t.false(prerelease.branchValidator({name: 'some-name', prerelease: false}));
-  t.false(prerelease.branchValidator({name: 'some-name', prerelease: '000'}));
-  t.false(prerelease.branchValidator({name: 'some-name', prerelease: '#beta'}));
-  t.false(prerelease.branchValidator({name: '000', prerelease: true}));
-  t.false(prerelease.branchValidator({name: '#beta', prerelease: true}));
-});
-
-test('The "prerelease" branches must have unique "prerelease" property', t => {
-  t.true(prerelease.branchesValidator([{prerelease: 'beta'}, {prerelease: 'alpha'}]));
-
-  t.false(prerelease.branchesValidator([{range: 'beta'}, {range: 'beta'}, {range: 'alpha'}]));
-});
-
-test('A "release" branch is identified by not havin a "range" or "prerelease" property or a "name" formatted like "N.x", "N.x.x" or "N.N.x"', t => {
-  t.true(release.filter({name: 'some-name'}));
-
-  t.false(release.filter({name: '1.x.x'}));
-  t.false(release.filter({name: '1.0.x'}));
-  t.false(release.filter({name: 'some-name', range: '1.x.x'}));
-  t.false(release.filter({name: 'some-name', range: '1.1.x'}));
-  t.false(release.filter({name: 'some-name', prerelease: true}));
-  t.false(release.filter({name: 'some-name', prerelease: 'beta'}));
-});
-
-test('There must be between 1 and 3 release branches', t => {
-  t.true(release.branchesValidator([{name: 'branch1'}]));
-  t.true(release.branchesValidator([{name: 'branch1'}, {name: 'branch2'}]));
-  t.true(release.branchesValidator([{name: 'branch1'}, {name: 'branch2'}, {name: 'branch3'}]));
-
-  t.false(release.branchesValidator([]));
-  t.false(release.branchesValidator([{name: 'branch1'}, {name: 'branch2'}, {name: 'branch3'}, {name: 'branch4'}]));
-});
@@ -33,16 +33,6 @@ test('The "publish" plugin output, if defined, must be an object or "false"', t
  t.true(plugins.publish.outputValidator(false));
 });

-test('The "addChannel" plugin output, if defined, must be an object', t => {
-  t.false(plugins.addChannel.outputValidator(1));
-  t.false(plugins.addChannel.outputValidator('string'));
-
-  t.true(plugins.addChannel.outputValidator({}));
-  t.true(plugins.addChannel.outputValidator());
-  t.true(plugins.addChannel.outputValidator(null));
-  t.true(plugins.addChannel.outputValidator(''));
-});
-
 test('The "generateNotes" plugins output are concatenated with separator and sensitive data is hidden', t => {
  const env = {MY_TOKEN: 'secret token'};
  t.is(plugins.generateNotes.postprocess(['note 1', 'note 2'], {env}), `note 1${RELEASE_NOTES_SEPARATOR}note 2`);
@@ -66,25 +66,6 @@ test('Get all commits since gitHead (from lastRelease) on a detached head repo',
  t.truthy(result[0].committer.name);
 });

-test('Get all commits between lastRelease.gitHead and a shas', async t => {
-  // Create a git repository, set the current working directory at the root of the repo
-  const {cwd} = await gitRepo();
-  // Add commits to the master branch
-  const commits = await gitCommits(['First', 'Second', 'Third'], {cwd});
-
-  // Retrieve the commits with the commits module, between commit 'First' and 'Third'
-  const result = await getCommits({
-    cwd,
-    lastRelease: {gitHead: commits[commits.length - 1].hash},
-    nextRelease: {gitHead: commits[1].hash},
-    logger: t.context.logger,
-  });
-
-  // Verify the commits created and retrieved by the module are identical
-  t.is(result.length, 1);
-  t.deepEqual(result, commits.slice(1, commits.length - 1));
-});
-
 test('Return empty array if lastRelease.gitHead is the last commit', async t => {
  // Create a git repository, set the current working directory at the root of the repo
  const {cwd} = await gitRepo();
@@ -6,7 +6,7 @@ import {omit} from 'lodash';
 import proxyquire from 'proxyquire';
 import {stub} from 'sinon';
 import yaml from 'js-yaml';
-import {gitRepo, gitTagVersion, gitCommits, gitShallowClone, gitAddConfig} from './helpers/git-utils';
+import {gitRepo, gitCommits, gitShallowClone, gitAddConfig} from './helpers/git-utils';

 const DEFAULT_PLUGINS = [
  '@semantic-release/commit-analyzer',
@@ -23,10 +23,8 @@ test.beforeEach(t => {
 test('Default values, reading repositoryUrl from package.json', async t => {
  const pkg = {repository: 'https://host.null/owner/package.git'};
  // Create a git repository, set the current working directory at the root of the repo
-  const {cwd} = await gitRepo(true);
+  const {cwd} = await gitRepo();
  await gitCommits(['First'], {cwd});
-  await gitTagVersion('v1.0.0', undefined, {cwd});
-  await gitTagVersion('v1.1.0', undefined, {cwd});
  // Add remote.origin.url config
  await gitAddConfig('remote.origin.url', 'git@host.null:owner/repo.git', {cwd});
  // Create package.json in repository root
@@ -35,35 +33,21 @@ test('Default values, reading repositoryUrl from package.json', async t => {
  const {options: result} = await t.context.getConfig({cwd});

  // Verify the default options are set
-  t.deepEqual(result.branches, [
-    '+([1-9])?(.{+([1-9]),x}).x',
-    'master',
-    'next',
-    'next-major',
-    {name: 'beta', prerelease: true},
-    {name: 'alpha', prerelease: true},
-  ]);
+  t.is(result.branch, 'master');
  t.is(result.repositoryUrl, 'https://host.null/owner/package.git');
  t.is(result.tagFormat, `v\${version}`);
 });

 test('Default values, reading repositoryUrl from repo if not set in package.json', async t => {
  // Create a git repository, set the current working directory at the root of the repo
-  const {cwd} = await gitRepo(true);
+  const {cwd} = await gitRepo();
  // Add remote.origin.url config
  await gitAddConfig('remote.origin.url', 'https://host.null/owner/module.git', {cwd});

  const {options: result} = await t.context.getConfig({cwd});

  // Verify the default options are set
-  t.deepEqual(result.branches, [
-    '+([1-9])?(.{+([1-9]),x}).x',
-    'master',
-    'next',
-    'next-major',
-    {name: 'beta', prerelease: true},
-    {name: 'alpha', prerelease: true},
-  ]);
+  t.is(result.branch, 'master');
  t.is(result.repositoryUrl, 'https://host.null/owner/module.git');
  t.is(result.tagFormat, `v\${version}`);
 });
@@ -78,14 +62,7 @@ test('Default values, reading repositoryUrl (http url) from package.json if not
  const {options: result} = await t.context.getConfig({cwd});

  // Verify the default options are set
-  t.deepEqual(result.branches, [
-    '+([1-9])?(.{+([1-9]),x}).x',
-    'master',
-    'next',
-    'next-major',
-    {name: 'beta', prerelease: true},
-    {name: 'alpha', prerelease: true},
-  ]);
+  t.is(result.branch, 'master');
  t.is(result.repositoryUrl, 'https://host.null/owner/module.git');
  t.is(result.tagFormat, `v\${version}`);
 });
@@ -108,7 +85,7 @@ test('Read options from package.json', async t => {
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
    generateNotes: 'generateNotes',
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -118,11 +95,10 @@ test('Read options from package.json', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from package.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from package.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Read options from .releaserc.yml', async t => {
@@ -130,7 +106,7 @@ test('Read options from .releaserc.yml', async t => {
  const {cwd} = await gitRepo();
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -140,11 +116,10 @@ test('Read options from .releaserc.yml', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from package.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from package.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Read options from .releaserc.json', async t => {
@@ -152,7 +127,7 @@ test('Read options from .releaserc.json', async t => {
  const {cwd} = await gitRepo();
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -162,11 +137,10 @@ test('Read options from .releaserc.json', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from package.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from package.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Read options from .releaserc.js', async t => {
@@ -174,7 +148,7 @@ test('Read options from .releaserc.js', async t => {
  const {cwd} = await gitRepo();
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -184,11 +158,10 @@ test('Read options from .releaserc.js', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from package.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from package.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Read options from release.config.js', async t => {
@@ -196,7 +169,7 @@ test('Read options from release.config.js', async t => {
  const {cwd} = await gitRepo();
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -206,11 +179,10 @@ test('Read options from release.config.js', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from package.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from package.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Prioritise CLI/API parameters over file configuration and git repo', async t => {
@@ -221,11 +193,11 @@ test('Prioritise CLI/API parameters over file configuration and git repo', async
  cwd = await gitShallowClone(repositoryUrl);
  const pkgOptions = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_pkg'},
-    branches: ['branch_pkg'],
+    branch: 'branch_pkg',
  };
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_cli'},
-    branches: ['branch_cli'],
+    branch: 'branch_cli',
    repositoryUrl: 'http://cli-url.com/owner/package',
    tagFormat: `cli\${version}`,
    plugins: false,
@@ -236,11 +208,10 @@ test('Prioritise CLI/API parameters over file configuration and git repo', async

  const result = await t.context.getConfig({cwd}, options);

-  const expected = {...options, branches: ['branch_cli']};
  // Verify the options contains the plugin config from CLI/API
-  t.deepEqual(result.options, expected);
+  t.deepEqual(result.options, options);
  // Verify the plugins module is called with the plugin options from CLI/API
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
 });

 test('Read configuration from file path in "extends"', async t => {
@@ -250,7 +221,7 @@ test('Read configuration from file path in "extends"', async t => {
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
    generateNotes: 'generateNotes',
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: ['plugin-1', ['plugin-2', {plugin2Opt: 'value'}]],
@@ -261,11 +232,10 @@ test('Read configuration from file path in "extends"', async t => {

  const {options: result} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from shareable.json
-  t.deepEqual(result, expected);
+  t.deepEqual(result, options);
  // Verify the plugins module is called with the plugin options from shareable.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
  t.deepEqual(t.context.plugins.args[0][1], {
    analyzeCommits: './shareable.json',
    generateNotes: './shareable.json',
@@ -281,7 +251,7 @@ test('Read configuration from module path in "extends"', async t => {
  const options = {
    analyzeCommits: {path: 'analyzeCommits', param: 'analyzeCommits_param'},
    generateNotes: 'generateNotes',
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -290,13 +260,12 @@ test('Read configuration from module path in "extends"', async t => {
  await outputJson(path.resolve(cwd, 'package.json'), {release: pkgOptions});
  await outputJson(path.resolve(cwd, 'node_modules/shareable/index.json'), options);

-  const {options: result} = await t.context.getConfig({cwd});
+  const {options: results} = await t.context.getConfig({cwd});

-  const expected = {...options, branches: ['test_branch']};
  // Verify the options contains the plugin config from shareable.json
-  t.deepEqual(result, expected);
+  t.deepEqual(results, options);
  // Verify the plugins module is called with the plugin options from shareable.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options});
  t.deepEqual(t.context.plugins.args[0][1], {
    analyzeCommits: 'shareable',
    generateNotes: 'shareable',
@@ -310,14 +279,14 @@ test('Read configuration from an array of paths in "extends"', async t => {
  const options1 = {
    verifyRelease: 'verifyRelease1',
    analyzeCommits: {path: 'analyzeCommits1', param: 'analyzeCommits_param1'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
  };
  const options2 = {
    verifyRelease: 'verifyRelease2',
    generateNotes: 'generateNotes2',
    analyzeCommits: {path: 'analyzeCommits2', param: 'analyzeCommits_param2'},
-    branches: ['test_branch'],
+    branch: 'test_branch',
    tagFormat: `v\${version}`,
    plugins: false,
  };
@@ -326,13 +295,12 @@ test('Read configuration from an array of paths in "extends"', async t => {
  await outputJson(path.resolve(cwd, 'shareable1.json'), options1);
  await outputJson(path.resolve(cwd, 'shareable2.json'), options2);

-  const {options: result} = await t.context.getConfig({cwd});
+  const {options: results} = await t.context.getConfig({cwd});

-  const expected = {...options1, ...options2, branches: ['test_branch']};
  // Verify the options contains the plugin config from shareable1.json and shareable2.json
-  t.deepEqual(result, expected);
+  t.deepEqual(results, {...options1, ...options2});
  // Verify the plugins module is called with the plugin options from shareable1.json and shareable2.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options: {...options1, ...options2}});
  t.deepEqual(t.context.plugins.args[0][1], {
    verifyRelease1: './shareable1.json',
    verifyRelease2: './shareable2.json',
@@ -347,7 +315,7 @@ test('Prioritize configuration from config file over "extends"', async t => {
  const {cwd} = await gitRepo();
  const pkgOptions = {
    extends: './shareable.json',
-    branches: ['test_pkg'],
+    branch: 'test_pkg',
    generateNotes: 'generateNotes',
    publish: [{path: 'publishPkg', param: 'publishPkg_param'}],
  };
@@ -355,7 +323,7 @@ test('Prioritize configuration from config file over "extends"', async t => {
    analyzeCommits: 'analyzeCommits',
    generateNotes: 'generateNotesShareable',
    publish: [{path: 'publishShareable', param: 'publishShareable_param'}],
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    tagFormat: `v\${version}`,
    plugins: false,
@@ -364,13 +332,12 @@ test('Prioritize configuration from config file over "extends"', async t => {
  await outputJson(path.resolve(cwd, 'package.json'), {release: pkgOptions});
  await outputJson(path.resolve(cwd, 'shareable.json'), options1);

-  const {options: result} = await t.context.getConfig({cwd});
+  const {options} = await t.context.getConfig({cwd});

-  const expected = omit({...options1, ...pkgOptions, branches: ['test_pkg']}, 'extends');
  // Verify the options contains the plugin config from package.json and shareable.json
-  t.deepEqual(result, expected);
+  t.deepEqual(options, omit({...options1, ...pkgOptions}, 'extends'));
  // Verify the plugins module is called with the plugin options from package.json and shareable.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {cwd, options: omit({...options, ...pkgOptions}, 'extends')});
  t.deepEqual(t.context.plugins.args[0][1], {
    analyzeCommits: './shareable.json',
    generateNotesShareable: './shareable.json',
@@ -383,13 +350,13 @@ test('Prioritize configuration from cli/API options over "extends"', async t =>
  const {cwd} = await gitRepo();
  const cliOptions = {
    extends: './shareable2.json',
-    branches: ['branch_opts'],
+    branch: 'branch_opts',
    publish: [{path: 'publishOpts', param: 'publishOpts_param'}],
    repositoryUrl: 'https://host.null/owner/module.git',
  };
  const pkgOptions = {
    extends: './shareable1.json',
-    branches: ['branch_pkg'],
+    branch: 'branch_pkg',
    generateNotes: 'generateNotes',
    publish: [{path: 'publishPkg', param: 'publishPkg_param'}],
  };
@@ -397,13 +364,13 @@ test('Prioritize configuration from cli/API options over "extends"', async t =>
    analyzeCommits: 'analyzeCommits1',
    generateNotes: 'generateNotesShareable1',
    publish: [{path: 'publishShareable', param: 'publishShareable_param1'}],
-    branches: ['test_branch1'],
+    branch: 'test_branch1',
    repositoryUrl: 'https://host.null/owner/module.git',
  };
  const options2 = {
    analyzeCommits: 'analyzeCommits2',
    publish: [{path: 'publishShareable', param: 'publishShareable_param2'}],
-    branches: ['test_branch2'],
+    branch: 'test_branch2',
    tagFormat: `v\${version}`,
    plugins: false,
  };
@@ -412,13 +379,15 @@ test('Prioritize configuration from cli/API options over "extends"', async t =>
  await outputJson(path.resolve(cwd, 'shareable1.json'), options1);
  await outputJson(path.resolve(cwd, 'shareable2.json'), options2);

-  const {options: result} = await t.context.getConfig({cwd}, cliOptions);
+  const {options} = await t.context.getConfig({cwd}, cliOptions);

-  const expected = omit({...options2, ...pkgOptions, ...cliOptions, branches: ['branch_opts']}, 'extends');
  // Verify the options contains the plugin config from package.json and shareable2.json
-  t.deepEqual(result, expected);
+  t.deepEqual(options, omit({...options2, ...pkgOptions, ...cliOptions}, 'extends'));
  // Verify the plugins module is called with the plugin options from package.json and shareable2.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {
+    cwd,
+    options: omit({...options2, ...pkgOptions, ...cliOptions}, 'extends'),
+  });
 });

 test('Allow to unset properties defined in shareable config with "null"', async t => {
@@ -427,7 +396,7 @@ test('Allow to unset properties defined in shareable config with "null"', async
  const pkgOptions = {
    extends: './shareable.json',
    analyzeCommits: null,
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
    plugins: null,
  };
@@ -458,7 +427,6 @@ test('Allow to unset properties defined in shareable config with "null"', async
    },
    cwd,
  });
-
  t.deepEqual(t.context.plugins.args[0][1], {
    generateNotes: './shareable.json',
    analyzeCommits: './shareable.json',
@@ -472,7 +440,7 @@ test('Allow to unset properties defined in shareable config with "undefined"', a
  const pkgOptions = {
    extends: './shareable.json',
    analyzeCommits: undefined,
-    branches: ['test_branch'],
+    branch: 'test_branch',
    repositoryUrl: 'https://host.null/owner/module.git',
  };
  const options1 = {
@@ -485,17 +453,18 @@ test('Allow to unset properties defined in shareable config with "undefined"', a
  await writeFile(path.resolve(cwd, 'release.config.js'), `module.exports = ${format(pkgOptions)}`);
  await outputJson(path.resolve(cwd, 'shareable.json'), options1);

-  const {options: result} = await t.context.getConfig({cwd});
+  const {options} = await t.context.getConfig({cwd});

-  const expected = {
-    ...omit(options1, 'analyzeCommits'),
-    ...omit(pkgOptions, ['extends', 'analyzeCommits']),
-    branches: ['test_branch'],
-  };
  // Verify the options contains the plugin config from shareable.json
-  t.deepEqual(result, expected);
+  t.deepEqual(options, {...omit(options1, 'analyzeCommits'), ...omit(pkgOptions, ['extends', 'analyzeCommits'])});
  // Verify the plugins module is called with the plugin options from shareable.json
-  t.deepEqual(t.context.plugins.args[0][0], {options: expected, cwd});
+  t.deepEqual(t.context.plugins.args[0][0], {
+    options: {
+      ...omit(options1, 'analyzeCommits'),
+      ...omit(pkgOptions, ['extends', 'analyzeCommits']),
+    },
+    cwd,
+  });
  t.deepEqual(t.context.plugins.args[0][1], {
    generateNotes: './shareable.json',
    analyzeCommits: './shareable.json',
@@ -511,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');
 });
@@ -8,7 +8,7 @@ test('Return the same "git" formatted URL if "gitCredentials" is not defined', a
  const {cwd} = await gitRepo();

  t.is(
-    await getAuthUrl({cwd, env, branch: {name: 'master'}, options: {repositoryUrl: 'git@host.null:owner/repo.git'}}),
+    await getAuthUrl({cwd, env, options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'}}),
    'git@host.null:owner/repo.git'
  );
 });
@@ -17,12 +17,7 @@ test('Return the same "https" formatted URL if "gitCredentials" is not defined',
  const {cwd} = await gitRepo();

  t.is(
-    await getAuthUrl({
-      cwd,
-      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'https://host.null/owner/repo.git'},
-    }),
+    await getAuthUrl({cwd, env, options: {branch: 'master', repositoryUrl: 'https://host.null/owner/repo.git'}}),
    'https://host.null/owner/repo.git'
  );
 });
@@ -31,12 +26,7 @@ test('Return the "https" formatted URL if "gitCredentials" is not defined and re
  const {cwd} = await gitRepo();

  t.is(
-    await getAuthUrl({
-      cwd,
-      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git+https://host.null/owner/repo.git'},
-    }),
+    await getAuthUrl({cwd, env, options: {branch: 'master', repositoryUrl: 'git+https://host.null/owner/repo.git'}}),
    'https://host.null/owner/repo.git'
  );
 });
@@ -45,7 +35,7 @@ test('Do not add trailing ".git" if not present in the origian URL', async t =>
  const {cwd} = await gitRepo();

  t.is(
-    await getAuthUrl({cwd, env, vranch: {name: 'master'}, options: {repositoryUrl: 'git@host.null:owner/repo'}}),
+    await getAuthUrl({cwd, env, options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo'}}),
    'git@host.null:owner/repo'
  );
 });
@@ -57,8 +47,7 @@ test('Handle "https" URL with group and subgroup', async t => {
    await getAuthUrl({
      cwd,
      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'https://host.null/group/subgroup/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'https://host.null/group/subgroup/owner/repo.git'},
    }),
    'https://host.null/group/subgroup/owner/repo.git'
  );
@@ -71,8 +60,7 @@ test('Handle "git" URL with group and subgroup', async t => {
    await getAuthUrl({
      cwd,
      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:group/subgroup/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:group/subgroup/owner/repo.git'},
    }),
    'git@host.null:group/subgroup/owner/repo.git'
  );
@@ -82,12 +70,7 @@ test('Convert shorthand URL', async t => {
  const {cwd} = await gitRepo();

  t.is(
-    await getAuthUrl({
-      cwd,
-      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'semanitc-release/semanitc-release'},
-    }),
+    await getAuthUrl({cwd, env, options: {repositoryUrl: 'semanitc-release/semanitc-release'}}),
    'https://github.com/semanitc-release/semanitc-release.git'
  );
 });
@@ -99,8 +82,7 @@ test('Convert GitLab shorthand URL', async t => {
    await getAuthUrl({
      cwd,
      env,
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'gitlab:semanitc-release/semanitc-release'},
+      options: {branch: 'master', repositoryUrl: 'gitlab:semanitc-release/semanitc-release'},
    }),
    'https://gitlab.com/semanitc-release/semanitc-release.git'
  );
@@ -113,8 +95,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined and reposi
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://user:pass@host.null/owner/repo.git'
  );
@@ -140,8 +121,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined and reposi
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'https://host.null/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'https://host.null/owner/repo.git'},
    }),
    'https://user:pass@host.null/owner/repo.git'
  );
@@ -154,8 +134,7 @@ test('Return the "http" formatted URL if "gitCredentials" is defined and reposit
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'http://host.null/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'http://host.null/owner/repo.git'},
    }),
    'http://user:pass@host.null/owner/repo.git'
  );
@@ -168,8 +147,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined and reposi
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git+https://host.null/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git+https://host.null/owner/repo.git'},
    }),
    'https://user:pass@host.null/owner/repo.git'
  );
@@ -182,8 +160,7 @@ test('Return the "http" formatted URL if "gitCredentials" is defined and reposit
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git+http://host.null/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git+http://host.null/owner/repo.git'},
    }),
    'http://user:pass@host.null/owner/repo.git'
  );
@@ -196,8 +173,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "GH_T
    await getAuthUrl({
      cwd,
      env: {...env, GH_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://token@host.null/owner/repo.git'
  );
@@ -210,8 +186,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "GITH
    await getAuthUrl({
      cwd,
      env: {...env, GITHUB_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://token@host.null/owner/repo.git'
  );
@@ -224,8 +199,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "GL_T
    await getAuthUrl({
      cwd,
      env: {...env, GL_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://gitlab-ci-token:token@host.null/owner/repo.git'
  );
@@ -238,8 +212,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "GITL
    await getAuthUrl({
      cwd,
      env: {...env, GITLAB_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://gitlab-ci-token:token@host.null/owner/repo.git'
  );
@@ -252,8 +225,7 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "BB_T
    await getAuthUrl({
      cwd,
      env: {...env, BB_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://x-token-auth:token@host.null/owner/repo.git'
  );
@@ -266,13 +238,25 @@ test('Return the "https" formatted URL if "gitCredentials" is defined with "BITB
    await getAuthUrl({
      cwd,
      env: {...env, BITBUCKET_TOKEN: 'token'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:owner/repo.git'},
    }),
    'https://x-token-auth:token@host.null/owner/repo.git'
  );
 });

+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();

@@ -280,8 +264,7 @@ test('Handle "https" URL with group and subgroup, with "GIT_CREDENTIALS"', async
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'https://host.null/group/subgroup/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'https://host.null/group/subgroup/owner/repo.git'},
    }),
    'https://user:pass@host.null/group/subgroup/owner/repo.git'
  );
@@ -294,8 +277,7 @@ test('Handle "git" URL with group and subgroup, with "GIT_CREDENTIALS', async t
    await getAuthUrl({
      cwd,
      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl: 'git@host.null:group/subgroup/owner/repo.git'},
+      options: {branch: 'master', repositoryUrl: 'git@host.null:group/subgroup/owner/repo.git'},
    }),
    'https://user:pass@host.null/group/subgroup/owner/repo.git'
  );
@@ -305,12 +287,7 @@ test('Do not add git credential to repositoryUrl if push is allowed', async t =>
  const {cwd, repositoryUrl} = await gitRepo(true);

  t.is(
-    await getAuthUrl({
-      cwd,
-      env: {...env, GIT_CREDENTIALS: 'user:pass'},
-      branch: {name: 'master'},
-      options: {repositoryUrl},
-    }),
+    await getAuthUrl({cwd, env: {...env, GIT_CREDENTIALS: 'user:pass'}, options: {branch: 'master', repositoryUrl}}),
    repositoryUrl
  );
 });
@@ -1,6 +1,7 @@
 import test from 'ava';
 import {stub} from 'sinon';
 import getLastRelease from '../lib/get-last-release';
+import {gitRepo, gitCommits, gitTagVersion, gitCheckout} from './helpers/git-utils';

 test.beforeEach(t => {
  // Stub the logger functions
@@ -8,61 +9,143 @@ test.beforeEach(t => {
  t.context.logger = {log: t.context.log};
 });

-test('Get the highest non-prerelease valid tag', t => {
-  const result = getLastRelease({
-    branch: {
-      name: 'master',
-      tags: [
-        {version: '2.0.0', gitTag: 'v2.0.0', gitHead: '222'},
-        {version: '1.0.0', gitTag: 'v1.0.0', gitHead: '111'},
-        {version: '3.0.0-beta.1', gitTag: 'v3.0.0-beta.1@beta', gitHead: '333'},
-      ],
-      type: 'release',
-    },
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
+test('Get the highest non-prerelease valid tag', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  // Create some commits and tags
+  await gitCommits(['First'], {cwd});
+  await gitTagVersion('foo', undefined, {cwd});
+  const commits = await gitCommits(['Second'], {cwd});
+  await gitTagVersion('v2.0.0', undefined, {cwd});
+  await gitCommits(['Third'], {cwd});
+  await gitTagVersion('v1.0.0', undefined, {cwd});
+  await gitCommits(['Fourth'], {cwd});
+  await gitTagVersion('v3.0', undefined, {cwd});
+  await gitCommits(['Fifth'], {cwd});
+  await gitTagVersion('v3.0.0-beta.1', undefined, {cwd});

-  t.deepEqual(result, {version: '2.0.0', gitTag: 'v2.0.0', name: 'v2.0.0', gitHead: '222', channel: undefined});
-  t.deepEqual(t.context.log.args[0][0], 'Found git tag v2.0.0 associated with version 2.0.0 on branch master');
+  const result = await getLastRelease({cwd, options: {tagFormat: `v\${version}`}, logger: t.context.logger});
+
+  t.deepEqual(result, {gitHead: commits[0].hash, gitTag: 'v2.0.0', version: '2.0.0'});
+  t.deepEqual(t.context.log.args[0], ['Found git tag v2.0.0 associated with version 2.0.0']);
 });

-test('Return empty object if no valid tag is found', t => {
-  const result = getLastRelease({
-    branch: {
-      name: 'master',
-      tags: [{version: '3.0.0-beta.1', gitTag: 'v3.0.0-beta.1@beta', gitHead: '111'}],
-      type: 'release',
-    },
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
+test('Get the highest tag in the history of the current branch', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  // Add commit to the master branch
+  await gitCommits(['First'], {cwd});
+  // Create the tag corresponding to version 1.0.0
+  // Create the new branch 'other-branch' from master
+  await gitCheckout('other-branch', true, {cwd});
+  // Add commit to the 'other-branch' branch
+  await gitCommits(['Second'], {cwd});
+  // Create the tag corresponding to version 3.0.0
+  await gitTagVersion('v3.0.0', undefined, {cwd});
+  // Checkout master
+  await gitCheckout('master', false, {cwd});
+  // Add another commit to the master branch
+  const commits = await gitCommits(['Third'], {cwd});
+  // Create the tag corresponding to version 2.0.0
+  await gitTagVersion('v2.0.0', undefined, {cwd});
+
+  const result = await getLastRelease({cwd, options: {tagFormat: `v\${version}`}, logger: t.context.logger});
+
+  t.deepEqual(result, {gitHead: commits[0].hash, gitTag: 'v2.0.0', version: '2.0.0'});
+});
+
+test('Match the tag name from the begining of the string', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  const commits = await gitCommits(['First'], {cwd});
+  await gitTagVersion('prefix/v1.0.0', undefined, {cwd});
+  await gitTagVersion('prefix/v2.0.0', undefined, {cwd});
+  await gitTagVersion('other-prefix/v3.0.0', undefined, {cwd});
+
+  const result = await getLastRelease({cwd, options: {tagFormat: `prefix/v\${version}`}, logger: t.context.logger});
+
+  t.deepEqual(result, {gitHead: commits[0].hash, gitTag: 'prefix/v2.0.0', version: '2.0.0'});
+});
+
+test('Return empty object if no valid tag is found', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  // Create some commits and tags
+  await gitCommits(['First'], {cwd});
+  await gitTagVersion('foo', undefined, {cwd});
+  await gitCommits(['Second'], {cwd});
+  await gitTagVersion('v2.0.x', undefined, {cwd});
+  await gitCommits(['Third'], {cwd});
+  await gitTagVersion('v3.0', undefined, {cwd});
+
+  const result = await getLastRelease({cwd, options: {tagFormat: `v\${version}`}, logger: t.context.logger});

  t.deepEqual(result, {});
-  t.deepEqual(t.context.log.args[0][0], 'No git tag version found on branch master');
+  t.is(t.context.log.args[0][0], 'No git tag version found');
 });

-test('Get the highest non-prerelease valid tag before a certain version', t => {
-  const result = getLastRelease(
-    {
-      branch: {
-        name: 'master',
-        channel: undefined,
-        tags: [
-          {version: '2.0.0', gitTag: 'v2.0.0', gitHead: '333'},
-          {version: '1.0.0', gitTag: 'v1.0.0', gitHead: '111'},
-          {version: '2.0.0-beta.1', gitTag: 'v2.0.0-beta.1@beta', gitHead: '222'},
-          {version: '2.1.0', gitTag: 'v2.1.0', gitHead: '444'},
-          {version: '2.1.1', gitTag: 'v2.1.1', gitHead: '555'},
-        ],
-        type: 'release',
-      },
-      options: {tagFormat: `v\${version}`},
-      logger: t.context.logger,
-    },
-    {before: '2.1.0'}
-  );
+test('Return empty object if no valid tag is found in history', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  await gitCommits(['First'], {cwd});
+  await gitCheckout('other-branch', true, {cwd});
+  await gitCommits(['Second'], {cwd});
+  await gitTagVersion('v1.0.0', undefined, {cwd});
+  await gitTagVersion('v2.0.0', undefined, {cwd});
+  await gitTagVersion('v3.0.0', undefined, {cwd});
+  await gitCheckout('master', false, {cwd});

-  t.deepEqual(result, {version: '2.0.0', gitTag: 'v2.0.0', name: 'v2.0.0', gitHead: '333', channel: undefined});
-  t.deepEqual(t.context.log.args[0][0], 'Found git tag v2.0.0 associated with version 2.0.0 on branch master');
+  const result = await getLastRelease({cwd, options: {tagFormat: `v\${version}`}, logger: t.context.logger});
+
+  t.deepEqual(result, {});
+  t.is(t.context.log.args[0][0], 'No git tag version found');
+});
+
+test('Get the highest valid tag corresponding to the "tagFormat"', async t => {
+  // Create a git repository, set the current working directory at the root of the repo
+  const {cwd} = await gitRepo();
+  // Create some commits and tags
+  const [{hash: gitHead}] = await gitCommits(['First'], {cwd});
+
+  await gitTagVersion('1.0.0', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `\${version}`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: '1.0.0',
+    version: '1.0.0',
+  });
+
+  await gitTagVersion('foo-1.0.0-bar', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `foo-\${version}-bar`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: 'foo-1.0.0-bar',
+    version: '1.0.0',
+  });
+
+  await gitTagVersion('foo-v1.0.0-bar', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `foo-v\${version}-bar`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: 'foo-v1.0.0-bar',
+    version: '1.0.0',
+  });
+
+  await gitTagVersion('(.+)/1.0.0/(a-z)', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `(.+)/\${version}/(a-z)`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: '(.+)/1.0.0/(a-z)',
+    version: '1.0.0',
+  });
+
+  await gitTagVersion('2.0.0-1.0.0-bar.1', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `2.0.0-\${version}-bar.1`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: '2.0.0-1.0.0-bar.1',
+    version: '1.0.0',
+  });
+
+  await gitTagVersion('3.0.0-bar.1', undefined, {cwd});
+  t.deepEqual(await getLastRelease({cwd, options: {tagFormat: `\${version}-bar.1`}, logger: t.context.logger}), {
+    gitHead,
+    gitTag: '3.0.0-bar.1',
+    version: '3.0.0',
+  });
 });
@@ -9,127 +9,33 @@ test.beforeEach(t => {
 });

 test('Increase version for patch release', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'master', type: 'release'},
-      nextRelease: {type: 'patch'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '1.0.1'
-  );
+  const version = getNextVersion({
+    nextRelease: {type: 'patch'},
+    lastRelease: {version: '1.0.0'},
+    logger: t.context.logger,
+  });
+  t.is(version, '1.0.1');
 });

 test('Increase version for minor release', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'master', type: 'release'},
-      nextRelease: {type: 'minor'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '1.1.0'
-  );
+  const version = getNextVersion({
+    nextRelease: {type: 'minor'},
+    lastRelease: {version: '1.0.0'},
+    logger: t.context.logger,
+  });
+  t.is(version, '1.1.0');
 });

 test('Increase version for major release', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'master', type: 'release'},
-      nextRelease: {type: 'major'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '2.0.0'
-  );
+  const version = getNextVersion({
+    nextRelease: {type: 'major'},
+    lastRelease: {version: '1.0.0'},
+    logger: t.context.logger,
+  });
+  t.is(version, '2.0.0');
 });

 test('Return 1.0.0 if there is no previous release', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'master', type: 'release'},
-      nextRelease: {type: 'minor'},
-      lastRelease: {},
-      logger: t.context.logger,
-    }),
-    '1.0.0'
-  );
-});
-
-test('Increase version for patch release on prerelease branch', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'patch'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '1.0.1-beta.1'
-  );
-
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'patch'},
-      lastRelease: {version: '1.0.0-beta.1'},
-      logger: t.context.logger,
-    }),
-    '1.0.0-beta.2'
-  );
-});
-
-test('Increase version for minor release on prerelease branch', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'minor'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '1.1.0-beta.1'
-  );
-
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'minor'},
-      lastRelease: {version: '1.0.0-beta.1'},
-      logger: t.context.logger,
-    }),
-    '1.0.0-beta.2'
-  );
-});
-
-test('Increase version for major release on prerelease branch', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'major'},
-      lastRelease: {version: '1.0.0'},
-      logger: t.context.logger,
-    }),
-    '2.0.0-beta.1'
-  );
-
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'major'},
-      lastRelease: {version: '1.0.0-beta.1'},
-      logger: t.context.logger,
-    }),
-    '1.0.0-beta.2'
-  );
-});
-
-test('Return 1.0.0 if there is no previous release on prerelease branch', t => {
-  t.is(
-    getNextVersion({
-      branch: {name: 'beta', type: 'prerelease', prerelease: 'beta'},
-      nextRelease: {type: 'minor'},
-      lastRelease: {},
-      logger: t.context.logger,
-    }),
-    '1.0.0-beta.1'
-  );
+  const version = getNextVersion({nextRelease: {type: 'minor'}, lastRelease: {}, logger: t.context.logger});
+  t.is(version, '1.0.0');
 });
@@ -1,258 +0,0 @@
-import test from 'ava';
-import {stub} from 'sinon';
-import getReleasesToAdd from '../lib/get-releases-to-add';
-
-test.beforeEach(t => {
-  // Stub the logger functions
-  t.context.log = stub();
-  t.context.logger = {log: t.context.log};
-});
-
-test('Return versions merged from release to maintenance branch', t => {
-  const result = getReleasesToAdd({
-    branch: {
-      name: '1.x',
-      channel: '1.x',
-      tags: [
-        {gitTag: 'v1.0.0@1.x', version: '1.0.0', channel: '1.x', gitHead: '111'},
-        {gitTag: 'v1.0.0', version: '1.0.0', gitHead: '111'},
-        {gitTag: 'v1.1.0', version: '1.1.0', gitHead: '222'},
-        {gitTag: 'v1.1.1', version: '1.1.1', gitHead: '333'},
-      ],
-    },
-    branches: [{name: '1.x', channel: '1.x'}, {name: 'master'}],
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
-
-  t.deepEqual(result, [
-    {
-      lastRelease: {version: '1.0.0', channel: '1.x', gitTag: 'v1.0.0@1.x', name: 'v1.0.0', gitHead: '111'},
-      currentRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: undefined,
-        gitTag: 'v1.1.0',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-      nextRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: '1.x',
-        gitTag: 'v1.1.0@1.x',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-    },
-    {
-      lastRelease: {version: '1.1.0', channel: undefined, gitTag: 'v1.1.0', name: 'v1.1.0', gitHead: '222'},
-      currentRelease: {
-        type: 'patch',
-        version: '1.1.1',
-        channel: undefined,
-        gitTag: 'v1.1.1',
-        name: 'v1.1.1',
-        gitHead: '333',
-      },
-      nextRelease: {
-        type: 'patch',
-        version: '1.1.1',
-        channel: '1.x',
-        gitTag: 'v1.1.1@1.x',
-        name: 'v1.1.1',
-        gitHead: '333',
-      },
-    },
-  ]);
-});
-
-test('Return versions merged from future branch to release branch', t => {
-  const result = getReleasesToAdd({
-    branch: {
-      name: 'master',
-      tags: [
-        {gitTag: 'v1.0.0', version: '1.0.0', gitHead: '111'},
-        {gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: '111'},
-        {gitTag: 'v1.1.0@next', version: '1.1.0', channel: 'next', gitHead: '222'},
-        {gitTag: 'v2.0.0@next-major', version: '2.0.0', channel: 'next-major', gitHead: '333'},
-      ],
-    },
-    branches: [{name: 'master'}, {name: 'next', channel: 'next'}, {name: 'next-major', channel: 'next-major'}],
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
-
-  t.deepEqual(result, [
-    {
-      lastRelease: {version: '1.0.0', channel: undefined, gitTag: 'v1.0.0', name: 'v1.0.0', gitHead: '111'},
-      currentRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: 'next',
-        gitTag: 'v1.1.0@next',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-      nextRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: undefined,
-        gitTag: 'v1.1.0',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-    },
-    {
-      lastRelease: {version: '1.1.0', gitTag: 'v1.1.0@next', name: 'v1.1.0', gitHead: '222', channel: 'next'},
-      currentRelease: {
-        type: 'major',
-        version: '2.0.0',
-        channel: 'next-major',
-        gitTag: 'v2.0.0@next-major',
-        name: 'v2.0.0',
-        gitHead: '333',
-      },
-      nextRelease: {
-        type: 'major',
-        version: '2.0.0',
-        channel: undefined,
-        gitTag: 'v2.0.0',
-        name: 'v2.0.0',
-        gitHead: '333',
-      },
-    },
-  ]);
-});
-
-test('Return releases sorted by ascending order', t => {
-  const result = getReleasesToAdd({
-    branch: {
-      name: 'master',
-      tags: [
-        {gitTag: 'v2.0.0@next-major', version: '2.0.0', channel: 'next-major', gitHead: '333'},
-        {gitTag: 'v1.1.0@next', version: '1.1.0', channel: 'next', gitHead: '222'},
-        {gitTag: 'v1.0.0', version: '1.0.0', gitHead: '111'},
-        {gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: '111'},
-      ],
-    },
-    branches: [{name: 'master'}, {name: 'next', channel: 'next'}, {name: 'next-major', channel: 'next-major'}],
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
-
-  t.deepEqual(result, [
-    {
-      lastRelease: {version: '1.0.0', channel: undefined, gitTag: 'v1.0.0', name: 'v1.0.0', gitHead: '111'},
-      currentRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: 'next',
-        gitTag: 'v1.1.0@next',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-      nextRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: undefined,
-        gitTag: 'v1.1.0',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-    },
-    {
-      lastRelease: {version: '1.1.0', gitTag: 'v1.1.0@next', name: 'v1.1.0', gitHead: '222', channel: 'next'},
-      currentRelease: {
-        type: 'major',
-        version: '2.0.0',
-        channel: 'next-major',
-        gitTag: 'v2.0.0@next-major',
-        name: 'v2.0.0',
-        gitHead: '333',
-      },
-      nextRelease: {
-        type: 'major',
-        version: '2.0.0',
-        channel: undefined,
-        gitTag: 'v2.0.0',
-        name: 'v2.0.0',
-        gitHead: '333',
-      },
-    },
-  ]);
-});
-
-test('no lastRelease', t => {
-  const result = getReleasesToAdd({
-    branch: {name: 'master', tags: [{gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: '111'}]},
-    branches: [{name: 'master'}, {name: 'next', channel: 'next'}],
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
-
-  t.deepEqual(result, [
-    {
-      lastRelease: {},
-      currentRelease: {
-        type: 'major',
-        version: '1.0.0',
-        channel: 'next',
-        gitTag: 'v1.0.0@next',
-        name: 'v1.0.0',
-        gitHead: '111',
-      },
-      nextRelease: {
-        type: 'major',
-        version: '1.0.0',
-        channel: undefined,
-        gitTag: 'v1.0.0',
-        name: 'v1.0.0',
-        gitHead: '111',
-      },
-    },
-  ]);
-});
-
-test('Ignore pre-release versions', t => {
-  const result = getReleasesToAdd({
-    branch: {
-      name: 'master',
-      tags: [
-        {gitTag: 'v1.0.0', version: '1.0.0', gitHead: '111'},
-        {gitTag: 'v1.0.0@next', version: '1.0.0', channel: 'next', gitHead: '111'},
-        {gitTag: 'v1.1.0@next', version: '1.1.0', channel: 'next', gitHead: '222'},
-        {gitTag: 'v2.0.0-alpha.1@alpha', version: '2.0.0', channel: 'alpha', gitHead: '333'},
-      ],
-    },
-    branches: [
-      {name: 'master'},
-      {name: 'next', channel: 'next'},
-      {name: 'alpha', type: 'prerelease', channel: 'alpha'},
-    ],
-    options: {tagFormat: `v\${version}`},
-    logger: t.context.logger,
-  });
-
-  t.deepEqual(result, [
-    {
-      lastRelease: {version: '1.0.0', channel: undefined, gitTag: 'v1.0.0', name: 'v1.0.0', gitHead: '111'},
-      currentRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: 'next',
-        gitTag: 'v1.1.0@next',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-      nextRelease: {
-        type: 'minor',
-        version: '1.1.0',
-        channel: undefined,
-        gitTag: 'v1.1.0',
-        name: 'v1.1.0',
-        gitHead: '222',
-      },
-    },
-  ]);
-});
@@ -3,14 +3,12 @@ import tempy from 'tempy';
 import {
  getTagHead,
  isRefInHistory,
-  isRefExists,
  fetch,
  getGitHead,
  repoUrl,
  tag,
  push,
  getTags,
-  getBranches,
  isGitRepo,
  verifyTagName,
  isBranchUpToDate,
@@ -44,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 => {
@@ -58,7 +56,7 @@ test('Unshallow and fetch repository', async t => {
  // Verify the shallow clone contains only one commit
  t.is((await gitGetCommits(undefined, {cwd})).length, 1);

-  await fetch('master', {cwd});
+  await fetch(repositoryUrl, {cwd});

  // Verify the shallow clone contains all the commits
  t.is((await gitGetCommits(undefined, {cwd})).length, 2);
@@ -66,15 +64,10 @@ test('Unshallow and fetch repository', async t => {

 test('Do not throw error when unshallow a complete repository', async t => {
  // Create a git repository, set the current working directory at the root of the repo
-  const {cwd, repositoryUrl} = await gitRepo(true);
+  const {cwd, repositoryUrl} = await gitRepo();
+  // Add commits to the master branch
  await gitCommits(['First'], {cwd});
-  await gitPush(repositoryUrl, 'master', {cwd});
-  await gitCheckout('second-branch', true, {cwd});
-  await gitCommits(['Second'], {cwd});
-  await gitPush(repositoryUrl, 'second-branch', {cwd});
-
-  await t.notThrows(fetch('master', {cwd}));
-  await t.notThrows(fetch('second-branch', {cwd}));
+  await t.notThrowsAsync(fetch(repositoryUrl, {cwd}));
 });

 test('Fetch all tags on a detached head repository', async t => {
@@ -89,7 +82,7 @@ test('Fetch all tags on a detached head repository', async t => {
  await gitPush(repositoryUrl, 'master', {cwd});
  cwd = await gitDetachedHead(repositoryUrl, commit.hash);

-  await fetch('master', {cwd});
+  await fetch(repositoryUrl, {cwd});

  t.deepEqual((await getTags({cwd})).sort(), ['v1.0.0', 'v1.0.1', 'v1.1.0'].sort());
 });
@@ -105,39 +98,9 @@ test('Verify if the commit `sha` is in the direct history of the current branch'
  const otherCommits = await gitCommits(['Second'], {cwd});
  await gitCheckout('master', false, {cwd});

-  t.true(await isRefInHistory(commits[0].hash, 'master', false, {cwd}));
-  t.falsy(await isRefInHistory(otherCommits[0].hash, 'master', false, {cwd}));
-  t.falsy(await isRefInHistory(otherCommits[0].hash, 'missing-branch', false, {cwd}));
-  await t.throws(isRefInHistory('non-existant-sha', 'master', false, {cwd}));
-});
-
-test('Verify if a branch exists', async t => {
-  // Create a git repository, set the current working directory at the root of the repo
-  const {cwd} = await gitRepo();
-  // Add commits to the master branch
-  await gitCommits(['First'], {cwd});
-  // Create the new branch 'other-branch' from master
-  await gitCheckout('other-branch', true, {cwd});
-  // Add commits to the 'other-branch' branch
-  await gitCommits(['Second'], {cwd});
-
-  t.true(await isRefExists('master', {cwd}));
-  t.true(await isRefExists('other-branch', {cwd}));
-  t.falsy(await isRefExists('next', {cwd}));
-});
-
-test('Get all branches', async t => {
-  const {cwd, repositoryUrl} = await gitRepo(true);
-  await gitCommits(['First'], {cwd});
-  await gitPush(repositoryUrl, 'master', {cwd});
-  await gitCheckout('second-branch', true, {cwd});
-  await gitCommits(['Second'], {cwd});
-  await gitPush(repositoryUrl, 'second-branch', {cwd});
-  await gitCheckout('third-branch', true, {cwd});
-  await gitCommits(['Third'], {cwd});
-  await gitPush(repositoryUrl, 'third-branch', {cwd});
-
-  t.deepEqual((await getBranches({cwd})).sort(), ['master', 'second-branch', 'third-branch'].sort());
+  t.true(await isRefInHistory(commits[0].hash, {cwd}));
+  t.falsy(await isRefInHistory(otherCommits[0].hash, {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 => {
@@ -183,7 +146,7 @@ test('Add tag on head commit', async t => {
  const {cwd} = await gitRepo();
  const commits = await gitCommits(['Test commit'], {cwd});

-  await tag('tag_name', 'HEAD', {cwd});
+  await tag('tag_name', {cwd});

  await t.is(await gitCommitTag(commits[0].hash, {cwd}), 'tag_name');
 });
@@ -193,13 +156,13 @@ test('Push tag to remote repository', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
  const commits = await gitCommits(['Test commit'], {cwd});

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

  t.is(await gitRemoteTagHead(repositoryUrl, 'tag_name', {cwd}), commits[0].hash);
 });

-test('Push tag to remote repository with remote branch ahead', async t => {
+test('Push tag to remote repository with remote branch ahaed', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
  const commits = await gitCommits(['First'], {cwd});
  await gitPush(repositoryUrl, 'master', {cwd});
@@ -207,7 +170,7 @@ test('Push tag to remote repository with remote branch ahead', async t => {
  await gitCommits(['Second'], {cwd: tmpRepo});
  await gitPush('origin', 'master', {cwd: tmpRepo});

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

  t.is(await gitRemoteTagHead(repositoryUrl, 'tag_name', {cwd}), commits[0].hash);
@@ -243,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 => {
@@ -1,7 +1,7 @@
 import tempy from 'tempy';
 import execa from 'execa';
 import fileUrl from 'file-url';
-import pEachSeries from 'p-each-series';
+import pReduce from 'p-reduce';
 import gitLogParser from 'git-log-parser';
 import getStream from 'get-stream';

@@ -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 pEachSeries(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);
 }
@@ -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;
 }

 /**
@@ -225,46 +227,3 @@ export function gitCommitTag(gitHead, execaOpts) {
 export async function gitPush(repositoryUrl = 'origin', branch = 'master', execaOpts) {
  await execa('git', ['push', '--tags', repositoryUrl, `HEAD:${branch}`], execaOpts);
 }
-
-/**
- * Merge a branch into the current one with `git merge`.
- *
- * @param {String} ref The ref to merge.
- * @param {Object} [execaOpts] Options to pass to `execa`.
- */
-export async function merge(ref, execaOpts) {
-  await execa('git', ['merge', '--no-ff', ref], execaOpts);
-}
-
-/**
- * Merge a branch into the current one with `git merge --ff`.
- *
- * @param {String} ref The ref to merge.
- * @param {Object} [execaOpts] Options to pass to `execa`.
- */
-export async function mergeFf(ref, execaOpts) {
-  await execa('git', ['merge', '--ff', ref], execaOpts);
-}
-
-/**
- * Merge a branch into the current one with `git rebase`.
- *
- * @param {String} ref The ref to merge.
- * @param {Object} [execaOpts] Options to pass to `execa`.
- */
-export async function rebase(ref, execaOpts) {
-  await execa('git', ['rebase', ref], execaOpts);
-}
-
-export async function changeAuthor(sha, execaOpts) {
-  await execa(
-    'git',
-    [
-      'filter-branch',
-      '-f',
-      '--env-filter',
-      `if [[ "$GIT_COMMIT" = "${sha}" ]]; then export GIT_COMMITTER_NAME="New Author" GIT_COMMITTER_EMAIL="author@test.com"; fi`,
-    ],
-    execaOpts
-  );
-}
@@ -1,5 +0,0 @@
-import execa from 'execa';
-
-export async function npmView(packageName, env) {
-  return JSON.parse(await execa.stdout('npm', ['view', packageName, '--json'], {env}));
-}
@@ -5,19 +5,8 @@ import {escapeRegExp} from 'lodash';
 import {writeJson, readJson} from 'fs-extra';
 import execa from 'execa';
 import {WritableStreamBuffer} from 'stream-buffers';
-import delay from 'delay';
 import {SECRET_REPLACEMENT} from '../lib/definitions/constants';
-import {
-  gitHead,
-  gitTagHead,
-  gitRepo,
-  gitCommits,
-  gitRemoteTagHead,
-  gitPush,
-  gitCheckout,
-  merge,
-} from './helpers/git-utils';
-import {npmView} from './helpers/npm-utils';
+import {gitHead, gitTagHead, gitRepo, gitCommits, gitRemoteTagHead, gitPush} from './helpers/git-utils';
 import gitbox from './helpers/gitbox';
 import mockServer from './helpers/mockserver';
 import npmRegistry from './helpers/npm-registry';
@@ -69,7 +58,7 @@ test('Release patch, minor and major versions', async t => {
    version: '0.0.0-dev',
    repository: {url: repositoryUrl},
    publishConfig: {registry: npmRegistry.url},
-    release: {branches: ['master', 'next'], success: false, fail: false},
+    release: {success: false, fail: false},
  });
  // Create a npm-shrinkwrap.json file
  await execa('npm', ['shrinkwrap'], {env: testEnv, cwd});
@@ -97,7 +86,7 @@ test('Release patch, minor and major versions', async t => {
  let createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
@@ -116,14 +105,15 @@ test('Release patch, minor and major versions', async t => {
  t.is((await readJson(path.resolve(cwd, 'npm-shrinkwrap.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  let {
-    'dist-tags': {latest: releasedVersion},
-  } = await npmView(packageName, testEnv);
+  let [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  let head = await gitHead({cwd});
  t.is(releasedVersion, version);
+  t.is(releasedGitHead, head);
  t.is(await gitTagHead(`v${version}`, {cwd}), head);
  t.is(await gitRemoteTagHead(authUrl, `v${version}`, {cwd}), head);
-  t.log(`+ released ${releasedVersion}`);
+  t.log(`+ released ${releasedVersion} with head ${releasedGitHead}`);

  await mockServer.verify(verifyMock);
  await mockServer.verify(createReleaseMock);
@@ -138,7 +128,7 @@ test('Release patch, minor and major versions', async t => {
  createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
@@ -157,14 +147,15 @@ test('Release patch, minor and major versions', async t => {
  t.is((await readJson(path.resolve(cwd, 'npm-shrinkwrap.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  ({
-    'dist-tags': {latest: releasedVersion},
-  } = await npmView(packageName, testEnv));
+  [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  head = await gitHead({cwd});
  t.is(releasedVersion, version);
+  t.is(releasedGitHead, head);
  t.is(await gitTagHead(`v${version}`, {cwd}), head);
  t.is(await gitRemoteTagHead(authUrl, `v${version}`, {cwd}), head);
-  t.log(`+ released ${releasedVersion}`);
+  t.log(`+ released ${releasedVersion} with head ${releasedGitHead}`);

  await mockServer.verify(verifyMock);
  await mockServer.verify(createReleaseMock);
@@ -179,7 +170,7 @@ test('Release patch, minor and major versions', async t => {
  createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
@@ -198,19 +189,20 @@ test('Release patch, minor and major versions', async t => {
  t.is((await readJson(path.resolve(cwd, 'npm-shrinkwrap.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  ({
-    'dist-tags': {latest: releasedVersion},
-  } = await npmView(packageName, testEnv));
+  [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  head = await gitHead({cwd});
  t.is(releasedVersion, version);
+  t.is(releasedGitHead, head);
  t.is(await gitTagHead(`v${version}`, {cwd}), head);
  t.is(await gitRemoteTagHead(authUrl, `v${version}`, {cwd}), head);
-  t.log(`+ released ${releasedVersion}`);
+  t.log(`+ released ${releasedVersion} with head ${releasedGitHead}`);

  await mockServer.verify(verifyMock);
  await mockServer.verify(createReleaseMock);

-  /* Major release on next */
+  /* Major release */
  version = '2.0.0';
  verifyMock = await mockServer.mock(
    `/repos/${owner}/${packageName}`,
@@ -220,18 +212,16 @@ test('Release patch, minor and major versions', async t => {
  createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}@next`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
  );

-  t.log('Commit a breaking change on next');
-  await gitCheckout('next', true, {cwd});
-  await gitPush('origin', 'next', {cwd});
+  t.log('Commit a breaking change');
  await gitCommits(['feat: foo\n\n BREAKING CHANGE: bar'], {cwd});
  t.log('$ semantic-release');
-  ({stdout, code} = await execa(cli, [], {env: {...env, TRAVIS_BRANCH: 'next'}, cwd}));
+  ({stdout, code} = await execa(cli, [], {env, cwd}));
  t.regex(stdout, new RegExp(`Published GitHub release: release-url/${version}`));
  t.regex(stdout, new RegExp(`Publishing version ${version} to npm registry`));
  t.is(code, 0);
@@ -241,67 +231,18 @@ test('Release patch, minor and major versions', async t => {
  t.is((await readJson(path.resolve(cwd, 'npm-shrinkwrap.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  ({
-    'dist-tags': {next: releasedVersion},
-  } = await npmView(packageName, testEnv));
+  [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  head = await gitHead({cwd});
  t.is(releasedVersion, version);
-  t.is(await gitTagHead(`v${version}@next`, {cwd}), head);
-  t.is(await gitRemoteTagHead(authUrl, `v${version}@next`, {cwd}), head);
-  t.log(`+ released ${releasedVersion} on @next`);
+  t.is(releasedGitHead, head);
+  t.is(await gitTagHead(`v${version}`, {cwd}), head);
+  t.is(await gitRemoteTagHead(authUrl, `v${version}`, {cwd}), head);
+  t.log(`+ released ${releasedVersion} with head ${releasedGitHead}`);

  await mockServer.verify(verifyMock);
  await mockServer.verify(createReleaseMock);
-
-  /* Merge next into master */
-  version = '2.0.0';
-  const releaseId = 1;
-  verifyMock = await mockServer.mock(
-    `/repos/${owner}/${packageName}`,
-    {headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}]},
-    {body: {permissions: {push: true}}, method: 'GET'}
-  );
-  const getReleaseMock = await mockServer.mock(
-    `/repos/${owner}/${packageName}/releases/tags/v2.0.0@next`,
-    {headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}]},
-    {body: {id: releaseId}, method: 'GET'}
-  );
-  const updateReleaseMock = await mockServer.mock(
-    `/repos/${owner}/${packageName}/releases/${releaseId}`,
-    {
-      body: {tag_name: `v${version}`, name: `v${version}`, prerelease: false},
-      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
-    },
-    {body: {html_url: `release-url/${version}`}, method: 'PATCH'}
-  );
-
-  t.log('Merge next into master');
-  await gitCheckout('master', false, {cwd});
-  await merge('next', {cwd});
-  await gitPush('origin', 'master', {cwd});
-  t.log('$ semantic-release');
-  ({stdout, code} = await execa(cli, [], {env, cwd}));
-  t.regex(stdout, new RegExp(`Updated GitHub release: release-url/${version}`));
-  t.regex(stdout, new RegExp(`Adding version ${version} to npm registry on dist-tag latest`));
-  t.is(code, 0);
-
-  // Wait for 3s as the change of dist-tag takes time to be reflected in the registry
-  await delay(3000);
-  // Retrieve the published package from the registry and check version and gitHead
-  ({
-    'dist-tags': {latest: releasedVersion},
-  } = await npmView(packageName, testEnv));
-  t.is(releasedVersion, version);
-  t.is(await gitTagHead(`v${version}`, {cwd}), await gitTagHead(`v${version}@next`, {cwd}));
-  t.is(
-    await gitRemoteTagHead(authUrl, `v${version}`, {cwd}),
-    await gitRemoteTagHead(authUrl, `v${version}@next`, {cwd})
-  );
-  t.log(`+ added ${releasedVersion}`);
-
-  await mockServer.verify(verifyMock);
-  await mockServer.verify(getReleaseMock);
-  await mockServer.verify(updateReleaseMock);
 });

 test('Exit with 1 if a plugin is not found', async t => {
@@ -317,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/);
 });
@@ -335,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/);
 });
@@ -356,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/);
 });
@@ -425,7 +366,7 @@ test('Allow local releases with "noCi" option', async t => {
  const createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
@@ -443,7 +384,9 @@ test('Allow local releases with "noCi" option', async t => {
  t.is((await readJson(path.resolve(cwd, 'package.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  const {version: releasedVersion, gitHead: releasedGitHead} = await npmView(packageName, testEnv);
+  const [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );

  const head = await gitHead({cwd});
  t.is(releasedVersion, version);
@@ -496,7 +439,9 @@ test('Pass options via CLI arguments', async t => {
  t.is((await readJson(path.resolve(cwd, 'package.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  const {version: releasedVersion, gitHead: releasedGitHead} = await npmView(packageName, testEnv);
+  const [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  const head = await gitHead({cwd});
  t.is(releasedVersion, version);
  t.is(releasedGitHead, head);
@@ -537,7 +482,7 @@ test('Run via JS API', async t => {
  const createReleaseMock = await mockServer.mock(
    `/repos/${owner}/${packageName}/releases`,
    {
-      body: {tag_name: `v${version}`, name: `v${version}`},
+      body: {tag_name: `v${version}`, target_commitish: 'master', name: `v${version}`},
      headers: [{name: 'Authorization', values: [`token ${env.GH_TOKEN}`]}],
    },
    {body: {html_url: `release-url/${version}`}}
@@ -552,7 +497,9 @@ test('Run via JS API', async t => {
  t.is((await readJson(path.resolve(cwd, 'package.json'))).version, version);

  // Retrieve the published package from the registry and check version and gitHead
-  const {version: releasedVersion, gitHead: releasedGitHead} = await npmView(packageName, testEnv);
+  const [, releasedVersion, releasedGitHead] = /^version = '(.+)'\s+gitHead = '(.+)'$/.exec(
+    (await execa('npm', ['show', packageName, 'version', 'gitHead'], {env: testEnv, cwd})).stdout
+  );
  const head = await gitHead({cwd});
  t.is(releasedVersion, version);
  t.is(releasedGitHead, head);
@@ -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');
@@ -152,24 +152,6 @@ test('Wrap "publish" plugin in a function that validate the output of the plugin
  t.regex(error.details, /2/);
 });

-test('Wrap "addChannel" plugin in a function that validate the output of the plugin', async t => {
-  const addChannel = stub().resolves(2);
-  const plugin = normalize(
-    {cwd, options: {}, stderr: t.context.stderr, logger: t.context.logger},
-    'addChannel',
-    addChannel,
-    {}
-  );
-
-  const error = await t.throws(plugin({options: {}}));
-
-  t.is(error.code, 'EADDCHANNELOUTPUT');
-  t.is(error.name, 'SemanticReleaseError');
-  t.truthy(error.message);
-  t.truthy(error.details);
-  t.regex(error.details, /2/);
-});
-
 test('Plugin is called with "pluginConfig" (with object definition) and input', async t => {
  const pluginFunction = stub().resolves();
  const pluginConf = {path: pluginFunction, conf: 'confValue'};
@@ -273,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));
@@ -1,166 +0,0 @@
-import test from 'ava';
-import AggregateError from 'aggregate-error';
-import {
-  extractErrors,
-  tagsToVersions,
-  isMajorRange,
-  isMaintenanceRange,
-  getUpperBound,
-  getLowerBound,
-  highest,
-  lowest,
-  getLatestVersion,
-  getEarliestVersion,
-  getFirstVersion,
-  getRange,
-  makeTag,
-} from '../lib/utils';
-
-test('extractErrors', t => {
-  const errors = [new Error('Error 1'), new Error('Error 2')];
-
-  t.deepEqual(extractErrors(new AggregateError(errors)), errors);
-  t.deepEqual(extractErrors(errors[0]), [errors[0]]);
-});
-
-test('tagsToVersions', t => {
-  t.deepEqual(tagsToVersions([{version: '1.0.0'}, {version: '1.1.0'}, {version: '1.2.0'}]), [
-    '1.0.0',
-    '1.1.0',
-    '1.2.0',
-  ]);
-});
-
-test('isMajorRange', t => {
-  t.false(isMajorRange('1.1.x'));
-  t.false(isMajorRange('1.11.x'));
-  t.false(isMajorRange('11.1.x'));
-  t.false(isMajorRange('11.11.x'));
-  t.false(isMajorRange('1.1.X'));
-  t.false(isMajorRange('1.1.0'));
-
-  t.true(isMajorRange('1.x.x'));
-  t.true(isMajorRange('11.x.x'));
-  t.true(isMajorRange('1.X.X'));
-  t.true(isMajorRange('1.x'));
-  t.true(isMajorRange('11.x'));
-  t.true(isMajorRange('1.X'));
-});
-
-test('isMaintenanceRange', t => {
-  t.true(isMaintenanceRange('1.1.x'));
-  t.true(isMaintenanceRange('11.1.x'));
-  t.true(isMaintenanceRange('11.11.x'));
-  t.true(isMaintenanceRange('1.11.x'));
-  t.true(isMaintenanceRange('1.x.x'));
-  t.true(isMaintenanceRange('11.x.x'));
-  t.true(isMaintenanceRange('1.x'));
-  t.true(isMaintenanceRange('11.x'));
-  t.true(isMaintenanceRange('1.1.X'));
-  t.true(isMaintenanceRange('1.X.X'));
-  t.true(isMaintenanceRange('1.X'));
-
-  t.false(isMaintenanceRange('1.1.0'));
-  t.false(isMaintenanceRange('11.1.0'));
-  t.false(isMaintenanceRange('1.11.0'));
-  t.false(isMaintenanceRange('11.11.0'));
-  t.false(isMaintenanceRange('~1.0.0'));
-  t.false(isMaintenanceRange('^1.0.0'));
-});
-
-test('getUpperBound', t => {
-  t.is(getUpperBound('1.x.x'), '2.0.0');
-  t.is(getUpperBound('1.x'), '2.0.0');
-  t.is(getUpperBound('1.0.x'), '1.1.0');
-  t.is(getUpperBound('1.0.0'), '1.0.0');
-
-  t.is(getUpperBound('foo'), undefined);
-});
-
-test('getLowerBound', t => {
-  t.is(getLowerBound('1.x.x'), '1.0.0');
-  t.is(getLowerBound('1.x'), '1.0.0');
-  t.is(getLowerBound('1.0.x'), '1.0.0');
-  t.is(getLowerBound('1.0.0'), '1.0.0');
-
-  t.is(getLowerBound('foo'), undefined);
-});
-
-test('highest', t => {
-  t.is(highest('1.0.0', '2.0.0'), '2.0.0');
-  t.is(highest('1.1.1', '1.1.0'), '1.1.1');
-  t.is(highest(null, '1.0.0'), '1.0.0');
-  t.is(highest('1.0.0'), '1.0.0');
-  t.is(highest(), undefined);
-});
-
-test('lowest', t => {
-  t.is(lowest('1.0.0', '2.0.0'), '1.0.0');
-  t.is(lowest('1.1.1', '1.1.0'), '1.1.0');
-  t.is(lowest(null, '1.0.0'), '1.0.0');
-  t.is(lowest(), undefined);
-});
-
-test.serial('getLatestVersion', t => {
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.1', '1.0.0-alpha.1']), '1.2.0');
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2']), undefined);
-
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.1', '1.0.0-alpha.1']), '1.2.0');
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2']), undefined);
-
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.1', '1.0.0-alpha.1'], {withPrerelease: true}), '1.2.3-alpha.3');
-  t.is(getLatestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2'], {withPrerelease: true}), '1.2.3-alpha.3');
-
-  t.is(getLatestVersion([]), undefined);
-});
-
-test.serial('getEarliestVersion', t => {
-  t.is(getEarliestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.0', '1.0.1-alpha.1']), '1.0.0');
-  t.is(getEarliestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2']), undefined);
-
-  t.is(getEarliestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.0', '1.0.1-alpha.1']), '1.0.0');
-  t.is(getEarliestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2']), undefined);
-
-  t.is(
-    getEarliestVersion(['1.2.3-alpha.3', '1.2.0', '1.0.1', '1.0.0-alpha.1'], {withPrerelease: true}),
-    '1.0.0-alpha.1'
-  );
-  t.is(getEarliestVersion(['1.2.3-alpha.3', '1.2.3-alpha.2'], {withPrerelease: true}), '1.2.3-alpha.2');
-
-  t.is(getEarliestVersion([]), undefined);
-});
-
-test('getFirstVersion', t => {
-  t.is(getFirstVersion(['1.2.0', '1.0.0', '1.3.0', '1.1.0', '1.4.0'], []), '1.0.0');
-  t.is(
-    getFirstVersion(
-      ['1.2.0', '1.0.0', '1.3.0', '1.1.0', '1.4.0'],
-      [
-        {name: 'master', tags: [{version: '1.0.0'}, {version: '1.1.0'}]},
-        {name: 'next', tags: [{version: '1.0.0'}, {version: '1.1.0'}, {version: '1.2.0'}]},
-      ]
-    ),
-    '1.3.0'
-  );
-  t.is(
-    getFirstVersion(
-      ['1.2.0', '1.0.0', '1.1.0'],
-      [
-        {name: 'master', tags: [{version: '1.0.0'}, {version: '1.1.0'}]},
-        {name: 'next', tags: [{version: '1.0.0'}, {version: '1.1.0'}, {version: '1.2.0'}]},
-      ]
-    ),
-    undefined
-  );
-});
-
-test('getRange', t => {
-  t.is(getRange('1.0.0', '1.1.0'), '>=1.0.0 <1.1.0');
-  t.is(getRange('1.0.0'), '>=1.0.0');
-});
-
-test('makeTag', t => {
-  t.is(makeTag(`v\${version}`, '1.0.0'), 'v1.0.0');
-  t.is(makeTag(`v\${version}`, '1.0.0', 'next'), 'v1.0.0@next');
-  t.is(makeTag(`v\${version}@test`, '1.0.0', 'next'), 'v1.0.0@next@test');
-});
@@ -5,9 +5,9 @@ import {gitRepo} from './helpers/git-utils';

 test('Throw a AggregateError', async t => {
  const {cwd} = await gitRepo();
-  const options = {branches: [{name: 'master'}, {name: ''}]};
+  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');
@@ -21,17 +21,13 @@ test('Throw a AggregateError', async t => {
  t.is(errors[2].code, 'ETAGNOVERSION');
  t.truthy(errors[2].message);
  t.truthy(errors[2].details);
-  t.is(errors[3].name, 'SemanticReleaseError');
-  t.is(errors[3].code, 'EINVALIDBRANCH');
-  t.truthy(errors[3].message);
-  t.truthy(errors[3].details);
 });

 test('Throw a SemanticReleaseError if does not run on a git repository', async t => {
  const cwd = tempy.directory();
-  const options = {branches: []};
+  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');
@@ -41,9 +37,9 @@ test('Throw a SemanticReleaseError if does not run on a git repository', async t

 test('Throw a SemanticReleaseError if the "tagFormat" is not valid', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
-  const options = {repositoryUrl, tagFormat: `?\${version}`, branches: []};
+  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');
@@ -53,9 +49,9 @@ test('Throw a SemanticReleaseError if the "tagFormat" is not valid', async t =>

 test('Throw a SemanticReleaseError if the "tagFormat" does not contains the "version" variable', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
-  const options = {repositoryUrl, tagFormat: 'test', branches: []};
+  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');
@@ -65,9 +61,9 @@ test('Throw a SemanticReleaseError if the "tagFormat" does not contains the "ver

 test('Throw a SemanticReleaseError if the "tagFormat" contains multiple "version" variables', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
-  const options = {repositoryUrl, tagFormat: `\${version}v\${version}`, branches: []};
+  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,43 +71,9 @@ test('Throw a SemanticReleaseError if the "tagFormat" contains multiple "version
  t.truthy(errors[0].details);
 });

-test('Throw a SemanticReleaseError for each invalid branch', async t => {
-  const {cwd, repositoryUrl} = await gitRepo(true);
-  const options = {
-    repositoryUrl,
-    tagFormat: `v\${version}`,
-    branches: [{name: ''}, {name: '  '}, {name: 1}, {}, {name: ''}, 1, 'master'],
-  };
-
-  const errors = [...(await t.throws(verify({cwd, options})))];
-
-  t.is(errors[0].name, 'SemanticReleaseError');
-  t.is(errors[0].code, 'EINVALIDBRANCH');
-  t.truthy(errors[0].message);
-  t.truthy(errors[0].details);
-  t.is(errors[1].name, 'SemanticReleaseError');
-  t.is(errors[1].code, 'EINVALIDBRANCH');
-  t.truthy(errors[1].message);
-  t.truthy(errors[1].details);
-  t.is(errors[2].name, 'SemanticReleaseError');
-  t.is(errors[2].code, 'EINVALIDBRANCH');
-  t.truthy(errors[2].message);
-  t.truthy(errors[2].details);
-  t.is(errors[3].name, 'SemanticReleaseError');
-  t.is(errors[3].code, 'EINVALIDBRANCH');
-  t.truthy(errors[3].message);
-  t.truthy(errors[3].details);
-  t.is(errors[4].code, 'EINVALIDBRANCH');
-  t.truthy(errors[4].message);
-  t.truthy(errors[4].details);
-  t.is(errors[5].code, 'EINVALIDBRANCH');
-  t.truthy(errors[5].message);
-  t.truthy(errors[5].details);
-});
-
 test('Return "true" if all verification pass', async t => {
  const {cwd, repositoryUrl} = await gitRepo(true);
-  const options = {repositoryUrl, tagFormat: `v\${version}`, branches: [{name: 'master'}]};
+  const options = {repositoryUrl, tagFormat: `v\${version}`};

-  await t.notThrows(verify({cwd, options}));
+  await t.notThrowsAsync(verify({cwd, options}));
 });
Author	SHA1	Message	Date
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
				`@@ -0,0 +1,2 @@`
				`# Package managers and languages (to be completed)`