Update hapi-auth-jwt2 to version 7.1.0 🚀 #89
Merged
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
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,
hapi-auth-jwt2 just published its new version 7.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 hapi-auth-jwt2.
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 15 commits .
352d4f6Adds ability to raise (custom) errors - for people who need extra control over the errors returned by thier API. defaults to standard Boom errors if an errorFunc is not defined. 100% backward compatible. (no change required) implemented by @jync in Add custom error raising. dwyl/hapi-auth-jwt2#183ef0d70badds CHANGELOG.md file informing people of the /releases list. fixes #1770725272Merge pull request #183 from HomePass/master4523688Merge pull request #186 from kamronbatman/patch-1b3475f4[README] Fixes typod5cb460Merge pull request #185 from jmm/verify-func-docs991b6ffFix typo, simplify91b3488Fix doc error: verified => unverified6fea0d8Add custom error raising.d570a28Merge pull request #178 from waldyrious/patch-1cce594bLICENSE: fix copyright line9bc8696add license title342907aMerge pull request #174 from wwalser/doc-update-disable-urlkeyf7b0486Updated docs to correctly point out how to disable urlKey.ffde771Merge pull request #173 from dwyl/v7.0.1See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade