Release v3.0.1

CHANGELOG.md

@@ -1,5 +1,10 @@
 
 
+## v3.0.1 - 2015-09-29
+- Release v3.0.1 / npm@v3.0.1
+- fix/update tests - ensure properties exists and works on 0.10
+- fix changelog (notice added properties are prefixed with **three underscores**)
+
 ## v3.0.0 - 2015-09-29
 - Release v3.0.0 / npm@v3.0.0
 - change prurpose of the library
@@ -9,7 +14,7 @@ Basically, because `native-or-bluebird` always try to use `bluebird` first and t
 
 So `native-or-another` is here to help and always will give you Promise, no matter what enviroment you use - iojs, 0.10, 0.11 or 0.12 or latest nodejs v4. It always will try to give you native Promsie first, otherwise will give you `bluebird` promise, but **remember, only if you don't give another** promise module like `q` or `promise` or what you want. See the example on README.md file.
 
-You also can check what promise you use. If you use custom promise `Promise` module, the constructor will have property called `__customPromise` with `true` value. If you use `Bluebird` you will have property on the constructor `__bluebirdPromise` and again with `true` value. Otherwise they won't exist.
+You also can check what promise you use. If you use custom promise `Promise` module, the constructor will have property called `___customPromise` (**yes, three underscores**) with `true` value. If you use `Bluebird` you will have property on the constructor `___bluebirdPromise` (**yes, three underscores**) and again with `true` value. Otherwise they won't exist.
 
 ## v2.0.0 - 2014-12-21
 - Release v2.0.0 / npm@v2.0.0

package.json

@@ -1,6 +1,6 @@
 {
   "name": "native-or-another",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "description": "Always will expose native `Promise` if available, otherwise `Bluebird` but only if you don't give another promise module like `q` or `promise` or what you want.",
   "repository": "tunnckoCore/native-or-another",
   "author": "Charlike Mike Reagent <@tunnckoCore> (http://www.tunnckocore.tk)",