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

Allow matching prereleases when validating plugin version requirements #4366

Merged
merged 2 commits into from
Jul 12, 2022

Conversation

devinivy
Copy link
Member

@devinivy devinivy commented Jul 11, 2022

Historically hapi has disallowed matching of prerelease versions when validating plugin requirements. This has caused some issues, e.g. when node's CITGM runs hapi's test suite on upcoming versions of node (hapijs/somever#18), or when testing plugins against the beta of hapi v21 (hapijs/inert#164 (comment)). In hapijs/somever#18 we resolved to change this behavior within hapi. This PR addresses the issue, following from adding the feature to somever in hapijs/somever#22.

I also updated the tests so that we don't trigger errors in the updated version of llhttp in node v18.5.0 (ref).

@devinivy devinivy added feature New functionality or improvement breaking changes Change that can breaking existing code labels Jul 11, 2022
@devinivy devinivy added this to the 21.0.0 milestone Jul 11, 2022
@devinivy devinivy added the test Test or coverage label Jul 11, 2022
@devinivy devinivy merged commit 7e7ea14 into v21 Jul 12, 2022
@devinivy devinivy deleted the include-prerelease branch July 12, 2022 12:24
@devinivy devinivy self-assigned this Jul 12, 2022
@devinivy devinivy mentioned this pull request Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking changes Change that can breaking existing code feature New functionality or improvement test Test or coverage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants