12.0.0 (2017-12-31)

Features

• make semantic-release CI agnostic (8d57565)

BREAKING CHANGES

• semantic-release doesn't make sure it runs only on one Travis job anymore.

The CI configuration has to be done such that semantic-release

• runs only once per build
• runs only after all tests are successful on every jobs of the build
• runs on Node >=8

This can easily be done with travis-deploy-once.

For Yarn users semantic-release has to be installed with the option --ignore-engines when running on Node <= 8.

See Can I use semantic-release with Yarn? for more details.

Migration Guide

Install travis-deploy-once:

$ npm install --save-dev travis-deploy-once

Add thetravis-deploy-once script in your package.json:

"scripts": {
    "semantic-release": "semantic-release",
    "travis-deploy-once": "travis-deploy-once"
  }

Modify your .travis.yml to use travis-deploy-once.
Replace:

after_success:
  - npm run semantic-release

by:
Replace

after_success:
  - npm run travis-deploy-once "npm run semantic-release"

For Yarn users or any project with a yarn.lock file, adds the --ignore-engines option to yarn install.
If the install is not defined you have to define it with:

install:
  - yarn install --ignore-engines