v6.0.0

<a name"6.0.0">

6.0.0 (2015-08-23)

Bug Fixes

• condition-travis: remove need for python script travis_after_all (4aa90880)

travis_after_all is a python script that had to be added to .travis.yml
manually to support testing multiple node versions. travis-after-all is the
same thing (even better actually, as it supports "allowed-failures") and can
be required. This is now part of the default verification plugin.

Breaking Changes

• If you run travis_after_all and travis-after-all at the same
  time they'll keep waiting for each other until forever. You have to apply
  this patch to your .travis.yml.

---
 .travis.yml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index a5fbddb..c76091b 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -14,9 +14,6 @@ before_install:
 - npm i -g npm@^2.0.0
 before_script:
 - npm prune
-- curl -Lo travis_after_all.py https://git.io/vLSON
 after_success:
-- python travis_after_all.py
-- export $(cat .to_export_back)
 - npm run semantic-release
--

(ef162321)

v4.3.3

<a name"4.3.3">

4.3.3 (2015-08-23)

Bug Fixes

• revert undeclared breaking change (5711e95c)

v5.0.1

<a name"5.0.1">

5.0.1 (2015-08-22)

Bug Fixes

• registry: be better at using the correct registry (relevant for npme) (45137811, closes #53)

v5.0.0

<a name"5.0.0">

5.0.0 (2015-08-22)

Features

• add fallbackTag functionality and map "next" to "latest" (7a4c89f1)

You can now map dist-tags onto "fallbackTags". E.g. if you want a
development channel like "next" and no version is currently published as "next"
semantic-release will fallback to "latest" to determine the new "next" version.
This is now the default for "next" -> "latest", but you can specify your own
mappings by adding "fallbackTags" to your package.json's "release" field.

Breaking Changes

• In cases where you pushed a new commit with a "dist-tag"
  configuration of "next" and no version was previously published as "next",
  semantic-release failed and did not publish a new version. It will now
  automatically fall back to the "latest" version to determine a new "next" version.

  (7a4c89f1)

v4.3.1

<a name"4.3.1">

4.3.1 (2015-08-22)

Bug Fixes

• registry: be better at using the correct registry (relevant for npme) (03534e51, closes #53)

v4.3.0

<a name"4.3.0">

4.3.0 (2015-08-22)

Features

• add fallbackTag functionality (360a5141)

You can now map dist-tags onto "fallbackTags". E.g. if you want a
development channel like "next" and no version is currently published as "next"
semantic-release could fallback to "latest" to determine the new "next" version.
You can specify your mappings by adding "fallbackTags" to your
package.json's "release" field.

v4.2.1

<a name"4.2.1">

4.2.1 (2015-08-22)

Bug Fixes

• commits: add helpful error when lastRelease not in history (5cc7da60, closes #61, #50)

v4.2.0

<a name"4.2.0">

4.2.0 (2015-08-22)

Bug Fixes

• clearer logput (7b8f6323)

Features

• plugins: run verifications in series (700ec9d4)

With this new feature you can pass an array of plugin locations/names to
both "verifyConditions" and "verifyRelease" in your package.json's "release"
field. This will run multiple verification plugins in series.

v4.1.1

<a name"4.1.1">

4.1.1 (2015-08-22)

Bug Fixes

• correctly obfuscate githubToken with verbose loglevel (b47311d5)

v4.1.0

<a name"4.1.0">

4.1.0 (2015-08-18)

Features

• plugins: add getLastRelease hook (7ceac766, closes #56)

Thank you @ariporad for implementing this!

Bug Fixes (via @semantic-release/last-release-npm)

• npm-registry-client: update to account for changes in registry replies (ad24990b) (npm/npm-registry-client#112)