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

15.0.3 (2018-03-13)

Bug Fixes

• convert git+https URL in package.json to https (b0b4fc8)
• use correct debug namespace (6f74dcb)

The new version differs by 3 commits.

• b0b4fc8 fix: convert git+https URL in package.json to https
• 6f74dcb fix: use correct debug namespace
• 1129d47 docs(configuration): environment variable DEBUG must be set to semantic-release:*, not semantic-release

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

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

15.5.0 (2018-05-21)

Features

• add support for git version 2.0.0 (47c73eb)
• verify minimum required git version is installed (db1cc60)

The new version differs by 2 commits.

• db1cc60 feat: verify minimum required git version is installed
• 47c73eb feat: add support for git version 2.0.0

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

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

15.0.2 (2018-03-08)

Bug Fixes

• exclude prereleases from version retrived by getLastRelease (e4618a2)

The new version differs by 1 commits.

• e4618a2 fix: exclude prereleases from version retrived by getLastRelease

See the full diff

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

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

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)

The new version differs by 1 commits .

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

See the full diff.

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