Merge tag '2.0.0'

no message

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Bowser Changelog
 
+### 2.0.0 (January 19, 2019)
+- [ADD] Support a non strict equality in `Parser.satisfies()` (#275)
+- [ADD] Add Android versions names (#276)
+- [ADD] Add a typings file (#277)
+- [ADD] Added support for Googlebot recognition (#278)
+- [FIX] Update building tools, avoid security issues
+
 ### 2.0.0-beta.3 (September 15, 2018)
 - [FIX] Fix Chrome Mobile detection (#253)
 - [FIX] Use built bowser for CI (#252)
@@ -82,7 +89,7 @@
 
 ### 1.5.0 (October 31, 2016)
 - [ADD] Throw an error when `minVersion` map has not a string as a version and fix readme (#165)
-- [FIX] Fix truly detection of Windows Phones (#167) 
+- [FIX] Fix truly detection of Windows Phones (#167)
 
 ### 1.4.6 (September 19, 2016)
 - [FIX] Fix mobile Opera's version detection on Android
@@ -120,4 +127,4 @@
 - [FEATURE] Add `bowser.check` method
 - [DOC] Changelog started
 - [DOC] Add API section to README
-- [FIX] Fix detection of browser type (A/C/X) for Chromium 
+- [FIX] Fix detection of browser type (A/C/X) for Chromium

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing
 
-The project runs Git-flow, where the `master` branch is the production one and the `develop` is the developing one.
+The project runs Git-flow, where the `master` branch is the development one and `production` is the production one.
 
-In a nutshell, if you're about to propose a new feature with adding new functionality to bowser, it's better to branch from `develop` and make a PR pointing to `develop` as well.
+In a nutshell, if you're about to propose a new feature with adding some totally new functionality to `bowser`, it's better to branch from `master` and make a PR pointing back to `master` as well.
-If it's a small hotfix, fix a typo in the docs or you've added support for a new browser/OS/platform/etc, then it's better to branch from `master` and make a PR pointing to `master` as well.
+If it's a small hotfix, fix a typo in the docs or you've added support for a new browser/OS/platform/etc, then it's better to branch from `production` and make a PR pointing back to `production`.
 Following these simple rules will help to maintain the repo a lot! Thanks ❤️

README.md

@@ -1,7 +1,7 @@
 ## Bowser
 A browser detector. Because sometimes, there is no other way, and not even good modern browsers always provide good feature detection mechanisms.
 
-[![Build Status](https://travis-ci.org/lancedikson/bowser.svg?branch=master)](https://travis-ci.org/lancedikson/bowser/) [![Greenkeeper badge](https://badges.greenkeeper.io/lancedikson/bowser.svg)](https://greenkeeper.io/)
+[![Build Status](https://travis-ci.org/lancedikson/bowser.svg?branch=master)](https://travis-ci.org/lancedikson/bowser/) [![Greenkeeper badge](https://badges.greenkeeper.io/lancedikson/bowser.svg)](https://greenkeeper.io/)[![Coverage Status](https://coveralls.io/repos/github/lancedikson/bowser/badge.svg?branch=master)](https://coveralls.io/github/lancedikson/bowser?branch=master)
 
 # Contents
 - [Overview](#overview)
@@ -129,10 +129,14 @@ Thus, you can define OS or platform specific rules and they will have more prior
 More of API and possibilities you will find in the `docs` folder.
 
 # Contributing
+
+We're always open to pull requests or code reviews. Everyone can become a permanent contributor. Just ping @lancedikson in the issues or on Twitter ❤️
+
 If you'd like to contribute a change to bowser, modify the files in `src/`, then run the following (you'll need node + npm installed):
 
 ``` sh
-$ npm install #build
+$ npm install
+$ npm run build #build
 $ npm test #run tests
 $ npm run lint #check lint rules
 ```

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "bowser",
-  "version": "2.0.0-beta.3",
+  "version": "2.0.0",
   "lockfileVersion": 1,
   "requires": true,
   "dependencies": {

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bowser",
-  "version": "2.0.0-beta.3",
+  "version": "2.0.0",
   "description": "Lightweight browser detector",
   "keywords": [
     "browser",