You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bell v10.0.0 is a release with hapi 18 support and support for the new LinkedIn api in the LinkedIn provider.
Breaking Changes
Support for hapi 18 (WHATWG URL usage)
The LinkedIn provider uses the new v2 api
Migration Checklist
hapi 18
Location headers won't have default ports in them anymore this is a side effect of hapi 18 using the WHATWG URL API
Make sure your flow still flows and that if you run your server on a default port your flow doesn't break because of the port missing in location headers
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
Bell v10.0.0 is a release with hapi 18 support and support for the new LinkedIn api in the LinkedIn provider.
Breaking Changes
Migration Checklist
hapi 18
LinkedIn v2 api
credentials.profile.raw.email
Contributors ❤️
This release was made possible due to these amazing people:
The text was updated successfully, but these errors were encountered: