Add sponsor link and put all migration docs in one file

Author: mikenicholson

README.md

@@ -151,21 +151,17 @@ Finally, the URL query parameters will be checked for a field matching either
 `options.tokenQueryParameterName` or `auth_token` if the option was not
 specified.
 
-## Migrating from 2.x.x to 3.x.x
+## Supporters
 
-Version 3.0.0 removes the `ExtractJwt.fromAuthHeader()` extractor function that would extract
-JWT's from `Authorization` headers with the auth scheme 'jwt'. The default authorization scheme
-of 'jwt' as the was not RFC 6750 compliant.  The extractor was replaced with 
-`ExtractJwt.fromAuthHeaderAsBearerToken()`.  The removal of `ExtractJwt.fromAuthHeader()` was done
-to clearly change the API so any code relying on the old API would clearly break, hopefully saving
-people some debugging time.
+This project is supported by
+![](http://passportjs.org/images/supported_logo.svg) [Auth0](https://auth0.com)
 
-If you want to maintain the behavior of `ExtractJwt.fromAuthHeader()` when switching to v3.3.0, simply 
-replace it with `ExtractJwt.fromAuthHeaderWithScheme('jwt')` in your implementation.
+If you want to quickly add secure token-based authentication to Node.js apps, feel free to check out Auth0's Node.js SDK and free plan at [auth0.com/overview](https://auth0.com/overview?utm_source=GHsponsor&utm_medium=GHsponsor&utm_campaign=passport-jwt&utm_content=auth)
 
-## Migrating from version 1.x.x to 2.x.x
- 
-See [the guide for migrating from v1 to v2](docs/migrating_v1_to_v2.md) for explanation of the major changes.
+## Migrating
+
+The the [Migration Guide](docs/migrating.md) for help upgrading to the latest
+major version of passport-jwt
 
 ## Tests
 

docs/migrating_v1_to_v2.md docs/migrating.md

@@ -1,4 +1,22 @@
-# Migrating from version 1.x.x to 2.x.x
+# Migration Guide
+
+The following instructions should help in migrating to a new major version of
+passport-jwt.
+
+## Migrating from 2.x.x to 3.x.x
+
+Version 3.0.0 removes the `ExtractJwt.fromAuthHeader()` extractor function that would extract
+JWT's from `Authorization` headers with the auth scheme 'jwt'. The default authorization scheme
+of 'jwt' as the was not RFC 6750 compliant.  The extractor was replaced with 
+`ExtractJwt.fromAuthHeaderAsBearerToken()`.  The removal of `ExtractJwt.fromAuthHeader()` was done
+to clearly change the API so any code relying on the old API would clearly break, hopefully saving
+people some debugging time.
+
+If you want to maintain the behavior of `ExtractJwt.fromAuthHeader()` when switching to v3.3.0, simply 
+replace it with `ExtractJwt.fromAuthHeaderWithScheme('jwt')` in your implementation.
+
+## Migrating from version 1.x.x to 2.x.x
+
 The v2 API is not backwards compatible with v1, specifically with regards to the introduction
 of the concept of JWT extractor functions.  If you require the legacy behavior in v1 you can use
 the extractor function ```versionOneCompatibility(options)```
@@ -35,5 +53,3 @@ opts.issuer = 'accounts.examplesoft.com';
 opts.audience = 'yoursite.net';
 passport.use(new JwtStrategy(opts, verifyFunction));
 ```
-
-