Update express-jwt to version 5.1.0 🚀 #63
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kunalkapadia
force-pushed
the
greenkeeper-express-jwt-5.1.0
branch
2 times, most recently
from
e7eaa82
to
c20d94a
Compare
kunalkapadia
force-pushed
the
greenkeeper-express-jwt-5.1.0
branch
from
c20d94a
to
8ccf29b
Compare
|
Changes Unknown when pulling c20d94a on greenkeeper-express-jwt-5.1.0 into * on develop*. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
express-jwt just published its new version 5.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of express-jwt.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 18 commits .
e7ed68c5.1.0fe12e32Merge pull request #135 from m31271n/mastera2c5408minorfbf15bdallow other auth schemes if credentialsRequired is false. closes #1294617101handle error on invalid tokens. Closes #134b723571A cleaner way to detect a function1dc27365.0.0acd25c7Merge branch 'siyangbi-master'8ef413bMerge branch 'master' of https://github.com/siyangbi/express-jwt into siyangbi-masterd0b660dMerge branch 'tactivos-master'b63bef9Merge branch 'master' of https://github.com/tactivos/express-jwt into tactivos-mastera7ab08a4.0.0b894ea2remove support for deprecated option01409b3upgrade jwt libraryfd58e89Update middleware to throw when token is invalid when credentials aren't requiredThere are 18 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade