Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bell 6 Release Notes #159

Closed
ldesplat opened this issue Oct 31, 2015 · 2 comments
Closed

Bell 6 Release Notes #159

ldesplat opened this issue Oct 31, 2015 · 2 comments
Labels
breaking changes Change that can breaking existing code feature New functionality or improvement release notes Major release documentation
Milestone
6.0.0

Comments

@ldesplat
Copy link
Contributor

How to upgrade

Update your application to node 4+ and Hapi 11+
You do not have to do anything else.

What changed

[ ] extendedProfile option used for all providers
[ ] consistent output in all providers except for raw (not all fields may be there, but put them in the same place)
[ ] Ensure all providers are using the latest published API
[x] Node 4+ only (Test 4.0, 4.x.x, 5.x.x)
[x] ES2015 (let, const, arrow functions, new style guide)
[x] Hapi 11+
[x] Updated all dependencies to latest node 4+ versions
[x] Better error message when not using https protocol and isSecure is true. See #162
@ldesplat ldesplat added feature New functionality or improvement breaking changes Change that can breaking existing code labels Oct 31, 2015
@ldesplat ldesplat added this to the 6.0.0 milestone Oct 31, 2015
@ldesplat ldesplat added the release notes Major release documentation label Nov 3, 2015
@ldesplat ldesplat changed the title Bell 6.x.x proposed breaking changes Bell 6 Release Notes Nov 3, 2015
@ldesplat
Copy link
Contributor Author

ldesplat commented Nov 3, 2015

After thinking about it a while, I won't change the oauth providers. No need to break people for not many benefits especially with how all providers are documented now.

This means, that only updating node and Hapi are the breaking changes.

@ldesplat ldesplat mentioned this issue Nov 3, 2015
Merged
@ldesplat ldesplat closed this as completed Nov 3, 2015
@lock
Copy link

lock bot commented Jan 9, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
breaking changes Change that can breaking existing code feature New functionality or improvement release notes Major release documentation
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
1 participant
@ldesplat