docs: breaking change

BREAKING CHANGE: 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`. ```diff --- .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 -- ```
docs(README): use equally sized, optimized talk thumbnails
2015-08-23 22:42:55 +02:00 · 2015-08-23 14:26:47 +02:00 · 2015-08-23 14:16:09 +02:00 · 2015-08-23 00:53:04 +02:00 · 2015-08-22 23:32:49 +02:00 · 2015-08-22 21:48:00 +02:00
3 changed files with 11 additions and 2 deletions
@@ -26,7 +26,7 @@ Out of the box this is just about _commit-messages_, but you can do so much more
 | **manual** | <pre><code><div>npm version major</div><div>git push origin master --tags</div><div>npm publish</div></code></pre> | You **manually decide** what the **next version** is. You have to remember what major, minor and patch means. You have to remember to push both commits and tags. You have to wait for the CI to pass. |
 | **semantic-release** | <pre><code><div>git commit -m "fix: &lt;message&gt;"</div><div>git push</div></code></pre> | You **describe the changes** you’ve made. A new version is automatically published with the correct version number.

-This removes the immediate connection between human emotions and version numbers, so strictly following the [SemVer](http://semver.org/) spec is not a problem anymore – and that’s ultimately `semantic-release`’s goal.
+This removes the immediate connection between human emotions and version numbers, so strictly following the [SemVer](http://semver.org/) spec is not a problem anymore – and that’s ultimately `semantic-release`’s goal.

 <table>
  <tr>
@@ -22,7 +22,7 @@
  },
  "dependencies": {
    "@semantic-release/commit-analyzer": "^2.0.0",
-    "@semantic-release/condition-travis": "^4.1.2",
+    "@semantic-release/condition-travis": "^4.1.0",
    "@semantic-release/error": "^1.0.0",
    "@semantic-release/last-release-npm": "^1.2.1",
    "@semantic-release/release-notes-generator": "^2.0.0",
@@ -66,6 +66,12 @@
  ],
  "license": "MIT",
  "main": "dist/index.js",
+  "publishConfig": {
+    "tag": "next"
+  },
+  "release": {
+    "branch": "next"
+  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/semantic-release/semantic-release.git"
@@ -25,6 +25,9 @@ const options = _.defaults(
  pkg.release,
  {
    branch: 'master',
+    fallbackTags: {
+      next: 'latest'
+    },
    debug: !env.CI,
    githubToken: env.GH_TOKEN || env.GITHUB_TOKEN,
    githubUrl: env.GH_URL
Author	SHA1	Message	Date
Stephan Bönnemann	ef1623210b	docs: breaking change BREAKING CHANGE: 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`. ```diff --- .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 -- ```	2015-08-23 22:42:55 +02:00
Stephan Bönnemann	ad9501540e	docs(README): use equally sized, optimized talk thumbnails	2015-08-23 14:26:47 +02:00
Stephan Bönnemann	7af30f0ad4	docs(README): list plugins and more talks	2015-08-23 14:16:09 +02:00
Stephan Bönnemann	4aa908804c	fix(condition-travis): remove need for python script travis_after_all	2015-08-23 00:53:04 +02:00
Stephan Bönnemann	451378117d	fix(registry): be better at using the correct registry (relevant for npme) Closes #53	2015-08-22 23:32:49 +02:00
Stephan Bönnemann	23221cc044	chore(package): update last-release-npm to 1.2.1	2015-08-22 21:48:00 +02:00
Stephan Bönnemann	7a4c89f131	feat: add fallbackTag functionality and map "next" to "latest" 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 CHANGE: In cases where you pushed a new commit with a "dist-tag" configuration of "next" and no version was previously published as "next", semanitc-release failed and did not publish a new version. It will now automatically fall back to to "latest".	2015-08-22 21:36:11 +02:00