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

[greenkeeper]

Version 6.3.2 of semantic-release just got published.

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

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

As semantic-release is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

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

Release Notes

v6.3.2

6.3.2 (2016-11-17)

Bug Fixes

• use travis-deploy-once to reenable travis-pro support (2be6e5d3)

We always want semantic-release to be simple and clean.

On versions 4 and below it requires a Python script, configured with 3 additional lines in your .travis.yml file, to get semantic-release to properly work with test matrices (i.e. testing multiple node versions).

In an attempt to fix this we published version 6 and on with a bundled JavaScript version of that script, so there was no need for additional config anymore.
Unfortunately though this broke compatibility with Travis Pro, because the JavaScript version does not support that. Version 6 never reached the "latest" dist-tag and stayed on "next" for quite some time, just because of this.

This has been the sad state of semantic-release for way too long, so we built travis-deploy-once. Another very simple JavaScript version of that script, but with out-of-the-box Travis Pro support.

So here it is: semantic-release 6.3.2. No more python script awkwardness in your .travis.yml files, no more latest/next confusion.

The last version on "latest" was 4.3.5 so here are the breaking changes that happened since then. Upgrading should be trivial.

From 6.0.0: 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)

From 5.0.0: 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)

Commits

The new version differs by 1 commits .

• 2be6e5d fix: use travis-deploy-once to reenable travis-pro support

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 6.3.1 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 6.3.6 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v6.3.6

<a name"6.3.6">

6.3.6 (2017-01-13)

Bug Fixes

• package:
  • update github to version 8.0.0 (afd6ab75)
  • update nopt to version 4.0.0 (b10c8910)

Commits

The new version differs by 19 commits0.

• af90de9 Merge pull request #355 from semantic-release/dep-updates
• aa012b3 Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
• 5724b19 Merge branch 'greenkeeper/github-8.0.0' into dep-updates
• 97a8e73 Merge branch 'caribou' into greenkeeper/nopt-4.0.0
• 51e12a3 docs(package): fix 'home' link
• afd6ab7 fix(package): update github to version 8.0.0
• f80e056 chore(package): update tap to version 9.0.0
• b10c891 fix(package): update nopt to version 4.0.0
• 3295f95 fix(package): update github to version 7.0.0
• 6a172e1 docs(README.md): discourage use of pre-patch, pre-minor and pre-release
• 68f9753 chore(package): update dependencies
• 462c51d style: standard
• cdf705c chore: update dependencies
• 9a51b02 chore: update github client
• 14618c8 chore(package): parse-github-repo-url

There are 19 commits in total.

See the full diff