This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of semantic-release.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
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.
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.
Coverage remained the same at 97.983% when pulling 8736808e668283c230649b88dc1971379f81dab4 on greenkeeper-semantic-release-6.3.2 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Coverage remained the same at 97.983% when pulling 8736808e668283c230649b88dc1971379f81dab4 on greenkeeper-semantic-release-6.3.2 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Hello lovely humans,
semantic-release just published its new version 6.3.2.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of semantic-release. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
6.3.2 (2016-11-17)
Bug Fixes
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
.travis.yml
.(ef162321)
From 5.0.0: Breaking Changes
(7a4c89f1)
The new version differs by 110 commits (ahead by 110, behind by 18).
2be6e5d
fix: use travis-deploy-once to reenable travis-pro support
a5cb9ea
fix(gitlog): increase maxBuffer
15e6daf
Merge pull request #262 from semantic-release/greenkeeper-npmlog-4.0.0
2326cda
chore(package): update npmlog to version 4.0.0
4afb280
chore(package): update tap to version 6.2.0 (#260)
7da7695
chore(package): update nyc to version 7.0.0 (#255)
41125ee
docs(readme): fix grammar
cca50ef
Merge pull request #212 from semantic-release/greenkeeper-nock-8.0.0
4807dee
Merge branch 'caribou' into greenkeeper-nock-8.0.0
f89792e
Merge pull request #226 from semantic-release/greenkeeper-run-auto-2.0.0
4078638
Merge branch 'caribou' into greenkeeper-run-auto-2.0.0
89ded2d
refactor(pre): adapt to new run-auto api
0a89265
Merge pull request #227 from aquavitae/caribou
ad2a615
feat(ssl): expose cafile from npm config
45e04be
chore(package): update run-auto to version 2.0.0
There are 110 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade