Skip to content

fix: support v18.x #1929

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 1 commit into from
Nov 28, 2022
Merged

fix: support v18.x #1929

merged 1 commit into from
Nov 28, 2022

Conversation

mmarchini
Copy link
Contributor

Co-authored-by: mary marchini [email protected]

Pre-Submission Checklist

  • Opened an issue discussing these changes before opening the PR
  • Ran the linter and tests via make prepush
  • Included comprehensive and convincing tests for changes

Issues

Closes:

  • Issue #
  • Issue #
  • Issue #

Summarize the issues that discussed these changes

Changes

What does this PR do?

@mmarchini mmarchini mentioned this pull request Nov 10, 2022
@acommodari
Copy link

Hey 👋
Just checking in to see what the status of this PR is. I would love to be able to upgrade to node 18 but even with restify v9 I'm still unable to because of the monkey-patch. Even a very broad ETA would be great so my team can plan the node upgrade accordingly.

Thank you in advance and thanks for all the great work getting version 9 released!

@mmarchini
Copy link
Contributor Author

We're aiming for the week of Nov 28

* Remove `closed()` monkey-patch, rely on connectionState instead (restifyGH-1888)
* fix IPv6 url by supporting new server.address().family format
* add node 18 to GH Actions

Co-authored-by: mary marchini <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants