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

Discontinued support for hapi v16 #3932

hueniverse opened this issue Mar 4, 2019 · 1 comment

Discontinued support for hapi v16 #3932

hueniverse opened this issue Mar 4, 2019 · 1 comment
breaking changes Change that can breaking existing code


Copy link

Active support for hapi@16.x.x was scheduled to end on March 1st, 2019. However, since the commercial support option is not yet available, support for hapi@16.x.x will be extended to March 31st, 2019.

When hapi@16.x.x is no longer supported, the npm modules for v16 will be officially deprecated. This will trigger an npm install warning, but otherwise will continue to work as usual. The same goes for all the core module dependencies versions used by hapi@16.x.x but not by more recent major versions.

Those still using hapi@16.x.x have the following options:

  • Do nothing - you will start seeing npm deprecation warning when you npm install your application and any bugs or security issues found will not be fixed. However, your application will continue to work exactly as-is today.

  • Upgrade to hapi@18 - for the latest features, fixes, and security, upgrade your application to use the latest version of the framework. The latest version is always free, supported, and most up to date.

  • Purchase a commercial license - while the license store is still being built, the upcoming license details are available. To keep your application using hapi v16 and still use a fully supported version of the framework, you must purchase a Plus level (v16 support until March 31st, 2020) or Enterprise level (v16 support until March 31st, 2021) license plan.

NOTE: if you plan to remain on hapi@16 and purchase a Plus or Enterprise plan, please contact before March 31st, 2019 to ensure a smooth transition. If you are a current project sponsor at a $500 level or higher, you will be receiving a customized offer to replace the sponsorship with a license when the store opens.

@hueniverse hueniverse added the breaking changes Change that can breaking existing code label Mar 4, 2019
@hueniverse hueniverse self-assigned this Mar 4, 2019
@hueniverse hueniverse added this to the 16.8.0 milestone Mar 25, 2019
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.
breaking changes Change that can breaking existing code
None yet

No branches or pull requests

1 participant