From 890255692f6119cd0a357ee9e1e5f9c1721bd314 Mon Sep 17 00:00:00 2001 From: Gregor Martynus Date: Sun, 17 May 2015 13:11:44 +0200 Subject: [PATCH] docs(readme): now also tested on io.js `^2` --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6690a9f1..3b982800 100644 --- a/README.md +++ b/README.md @@ -171,7 +171,7 @@ It is indeed a great idea because it _forces_ you to follow best practices. If y ### Why should I trust `semantic-release` with my releases? What if it breaks? -`semantic-release` has a full integration-test suite that tests _actual_ `npm` publishes and _actual_ GitHub Releases (with private registry/API) on node.js `^0.10`, `^0.12` and io.js `^1`. A new version won't get published if it doesn't pass on all these engines. +`semantic-release` has a full integration-test suite that tests _actual_ `npm` publishes and _actual_ GitHub Releases (with private registry/API) on node.js `^0.10`, `^0.12` and io.js `^1`, `^2`. A new version won't get published if it doesn't pass on all these engines. ## License