		@@ -1,3 +0,6 @@
		## [HEAD](https://github.com/mjrussell/redux-auth-wrapper/compare/v1.1.0...master)
		## [HEAD](https://github.com/mjrussell/redux-auth-wrapper/compare/v1.1.1...master)

		## [1.1.1](https://github.com/mjrussell/redux-auth-wrapper/compare/v1.1.0...v1.1.1)
		- Update: Bump and loosen prop-types dependency to get rid of audit warnings [#279](https://github.com/mjrussell/redux-auth-wrapper/pull/278) (Contributed by @bj00rn)

		## [1.1.0](https://github.com/mjrussell/redux-auth-wrapper/compare/v1.0.0...v1.1.0)
		@@ -4,0 +7,0 @@ - Feature: Support hash fragments in building the redirect location [#121](https://github.com/mjrussell/redux-auth-wrapper/issues/121)

package.json

		{
		"name": "redux-auth-wrapper",
		"version": "1.1.0",
		"version": "1.1.1",
		"description": "A utility library for handling authentication and authorization for redux and react-router",
		@@ -13,5 +13,5 @@ "main": "lib/index.js",
		"scripts": {
		"build": "mkdir -p lib && babel ./src --out-dir ./lib",
		"build": "mkdirp lib && babel ./src --out-dir ./lib",
		"lint": "eslint src test",
		"prepublish": "rm -rf lib && npm run build",
		"prepublish": "rimraf lib && npm run build",
		"test": "mocha --compilers js:babel-core/register --recursive --require test/init.js test/*/-test.js",
		@@ -49,2 +49,3 @@ "test:cov": "babel-node --max-old-space-size=4076 $(npm bin)/babel-istanbul cover $(npm bin)/_mocha -- --require test/init.js test/*/-test.js",
		"lodash": "4.16.6",
		"mkdirp": "^0.5.1",
		"mocha": "3.1.2",
		@@ -58,2 +59,3 @@ "react": "15.3.2",
		"redux": "3.6.0",
		"rimraf": "^2.6.1",
		"sinon": "1.17.6",
		@@ -65,4 +67,4 @@ "webpack": "1.13.3"
		"lodash.isempty": "4.4.0",
		"prop-types": "15.5.8"
		"prop-types": "^15.5.7"
		}
		}

README.md

		@@ -30,3 +30,3 @@ # redux-auth-wrapper

		At first, handling authentication and authorization seems easy in React-Router and Redux. After all, we have a handy [onEnter](https://github.com/rackt/react-router/blob/master/docs/API.md#onenternextstate-replace-callback) method, shouldn't we use it?
		At first, handling authentication and authorization seems easy in React-Router and Redux. After all, we have a handy [onEnter](https://github.com/ReactTraining/react-router/blob/v3/docs/API.md#onenternextstate-replace-callback) method, shouldn't we use it?

		@@ -33,0 +33,0 @@ `onEnter` is great, and useful in certain situations. However, here are some common authentication and authorization problems `onEnter` does not solve:

redux-auth-wrapper - npm Package Compare versions

Improved metrics