Skip to content

Revert "Update dependencies accept & boom to new namespace (#3089)" #3111

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

Merged
merged 2 commits into from
Jul 30, 2019

Conversation

abernix
Copy link
Member

@abernix abernix commented Jul 30, 2019

This reverts commits 0de2942, 97b3f68 and 293e28d.

While the change in #3089 change was seemingly justified and straightforward
(and as #3106 points out, perhaps too straightforward! 😄), it seems
that there was more to the change from accept to @hapi/accept and boom
to @hapi/boom than just a name change. It seems that the packages may
have dropped support for Node.js 6.

While Node.js 6 is no longer supported by the Node Foundation, for
semantic versioning reasons we weren't intending to completely drop support
for it until Apollo Server 3.x.

Maybe there's a more granular update here that maintains this support, but
this update wasn't as simple as it would have seemed to be at face value
(i.e. not a straight package rename of an otherwise internal dependency).

Happy to consider re-landing a similar thing, but we need to make it more
clear in the CHANGELOG.md and possibly reserve it for Apollo Server 3.x,
but for now, should revert this to make sure we're not shipping a broken
integration for Hapi users, as reported in #3106.

abernix added 2 commits July 31, 2019 00:32
This reverts commits 0de2942, 97b3f68 and 293e28d.

While the change in #3089 change was seemingly justified and straightforward
(and as #3106 points out, perhaps _too_ straightforward!  😄), it seems
that there was more to the change from `accept` to `@hapi/accept` and `boom`
to `@hapi/boom` than just a name change.  It seems that the packages may
have dropped support for Node.js 6.

While Node.js 6 is no longer supported by the Node Foundation, for
semantic versioning reasons we weren't intending to completely drop support
for it until Apollo Server 3.x.

Maybe there's a more granular update here that maintains this support, but
this update wasn't as simple as it would have seemed to be at face value
(i.e. not a straight package rename of an otherwise internal dependency).

Happy to consider re-landing a similar thing, but we need to make it more
clear in the `CHANGELOG.md` and possibly reserve it for Apollo Server 3.x,
but for now, should revert this to make sure we're not shipping a broken
integration for Hapi users, as reported in #3106.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@abernix abernix merged commit 0d27c58 into master Jul 30, 2019
@abernix abernix deleted the abernix/undo-pr-3106 branch July 30, 2019 21:43
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant