fix: use travis-deploy-once to reenable travis-pro support

This is needed for repositories with a lot of commits and/or a big changelog.

Closes #286

README.md

@@ -79,9 +79,9 @@ This removes the immediate connection between human emotions and version numbers
 
 Instead of writing [meaningless commit messages](http://whatthecommit.com/), we can take our time to think about the changes in the codebase and write them down. Following formalized conventions it is then possible to generate a helpful changelog and to derive the next semantic version number from them.
 
-When `semantic-release` got setup it will do that after every successful continuous integration build of your master branch (or any other branch you specify) and publish the new version for you. That way no human is directly involved in the release process and your releases are guaranteed to be [unromantic and unsentimental](http://sentimentalversioning.org/).
+When `semantic-release` is setup it will do that after every successful continuous integration build of your master branch (or any other branch you specify) and publish the new version for you. This way no human is directly involved in the release process and your releases are guaranteed to be [unromantic and unsentimental](http://sentimentalversioning.org/).
 
-If you fear the loss of control over timing and marketing implications of software releases you should know that `semantic-release` supports [release channels](https://github.com/npm/npm/issues/2718) using `npm`’s [dist-tags](https://docs.npmjs.com/cli/dist-tag). This way you can keep control over what your users end up using by default, you can decide when to promote an automatically released version to the stable channel and you can choose which versions to write blogposts and tweets about. You can use the same mechanism to [support older versions of your software](https://gist.github.com/boennemann/54042374e49c7ade8910), for example with important security fixes.
+If you fear the loss of control over timing and marketing implications of software releases you should know that `semantic-release` supports [release channels](https://github.com/npm/npm/issues/2718) using `npm`’s [dist-tags](https://docs.npmjs.com/cli/dist-tag). This way you can keep control over what your users end up using by default, you can decide when to promote an automatically released version to the stable channel, and you can choose which versions to write blogposts and tweets about. You can use the same mechanism to [support older versions of your software](https://gist.github.com/boennemann/54042374e49c7ade8910), for example with important security fixes.
 
 This is what happens in series:
 

bin/semantic-release.js

@@ -52,6 +52,7 @@ npmconf.load({}, function (err, conf) {
     auth: {
       token: env.NPM_TOKEN
     },
+    cafile: conf.get('cafile'),
     loglevel: conf.get('loglevel'),
     registry: require('../src/lib/get-registry')(pkg, conf),
     tag: (pkg.publishConfig || {}).tag || conf.get('tag') || 'latest'

package.json

@@ -15,7 +15,7 @@
   "dependencies": {
     "@bahmutov/parse-github-repo-url": "^0.1.0",
     "@semantic-release/commit-analyzer": "^2.0.0",
-    "@semantic-release/condition-travis": "^5.0.0",
+    "@semantic-release/condition-travis": "^5.0.2",
     "@semantic-release/error": "^1.0.0",
     "@semantic-release/last-release-npm": "^1.2.1",
     "@semantic-release/release-notes-generator": "^2.0.0",
@@ -26,9 +26,9 @@
     "nopt": "^3.0.3",
     "normalize-package-data": "^2.3.4",
     "npmconf": "^2.1.2",
-    "npmlog": "^2.0.0",
+    "npmlog": "^4.0.0",
     "require-relative": "^0.8.7",
-    "run-auto": "^1.1.2",
+    "run-auto": "^2.0.0",
     "run-series": "^1.1.3",
     "semver": "^5.0.3"
   },
@@ -37,13 +37,13 @@
     "cz-conventional-changelog": "^1.1.4",
     "mkdirp": "^0.5.1",
     "nixt": "^0.5.0",
-    "nock": "^7.0.1",
+    "nock": "^8.0.0",
     "npm-registry-couchapp": "^2.6.11",
-    "nyc": "^6.1.1",
+    "nyc": "^7.0.0",
     "proxyquire": "^1.7.3",
     "rimraf": "^2.5.0",
     "standard": "^7.0.1",
-    "tap": "^5.0.0"
+    "tap": "^6.2.0"
   },
   "engines": {
     "node": ">=0.10",

src/lib/commits.js

@@ -49,6 +49,9 @@ module.exports = function (config, cb) {
   function extract () {
     exec(
       'git log -E --format=%H==SPLIT==%B==END== ' + range,
+      {
+        maxBuffer: 1024 * 1024 // 1MB instead of 220KB (issue #286)
+      },
       function (err, stdout) {
         if (err) return cb(err)
 

src/pre.js

@@ -10,13 +10,13 @@ module.exports = function (config, cb) {
 
   auto({
     lastRelease: plugins.getLastRelease.bind(null, config),
-    commits: ['lastRelease', function (cb, results) {
+    commits: ['lastRelease', function (results, cb) {
       getCommits(_.assign({
         lastRelease: results.lastRelease
       }, config),
       cb)
     }],
-    type: ['commits', 'lastRelease', function (cb, results) {
+    type: ['commits', 'lastRelease', function (results, cb) {
       getType(_.assign({
         commits: results.commits,
         lastRelease: results.lastRelease

test/mocks/child-process.js

@@ -4,7 +4,10 @@ const rawCommits = [
 ]
 
 module.exports = {
-  exec: function (command, cb) {
+  exec: function (command, options, cb) {
+    if (typeof cb === 'undefined' && typeof options === 'function') {
+      cb = options
+    }
     if (/contains/.test(command)) {
       if (/notinhistory/.test(command)) return cb(new Error())
       return cb(null, 'whatever\nmaster\n')