Skip to content

Conversation

@mvolz
Copy link
Collaborator

@mvolz mvolz commented Oct 22, 2024

Due to localhost now pointing to IPv6 instead of IPv4 as of node 18, TestServer now explicitly serves 127.0.0.1 instead of localhost.

Consumers who import the TestServer from service runner will need to update their test runner applications to serve from 127.0.0.1 as well in order to upgrade from node16 to node 18, in addition to upgrading from 5.0.0 to 6.0.0.

@mvolz mvolz requested a review from jdforrester October 22, 2024 10:09
@jdforrester
Copy link
Member

The breaking change part of this PR is OK, but tagging this particular patch as the 6.0.0 release seems premature?

@mvolz mvolz changed the title Require node 18 or higher, update to 6.0.0 Require node 18 or higher, update to 5.1.0 Oct 29, 2024
@mvolz
Copy link
Collaborator Author

mvolz commented Oct 29, 2024

Better? :)

@jdforrester
Copy link
Member

Better? :)

No, worse. This is a breaking change, so the next release will definitely be 6.0.0. I just don't think this MR should be considered the release point.

@mvolz
Copy link
Collaborator Author

mvolz commented Oct 29, 2024

This release point includes this breaking change: f4f793f

I would like to release it ASAP as it's blocking us from updating citoid to 18 and 20.

Due to localhost now pointing to IPv6 instead of IPv4 as of node 18, TestServer now explicitly serves 127.0.0.1 instead of localhost.

Consumers who import the TestServer from service runner will need to update their test runner applications to serve from 127.0.0.1 as well in order to upgrade from node16 to node 18, in addition to upgrading from 5.0.0 to 6.0.0.
@mvolz mvolz changed the title Require node 18 or higher, update to 5.1.0 Require node 18 or higher, update to 6.0.0 Oct 29, 2024
@edg2s
Copy link
Member

edg2s commented Nov 1, 2024

What else needs to be in this release? I'm happy for this to go as is...

@jdforrester
Copy link
Member

What else needs to be in this release? I'm happy for this to go as is...

If we're doing this, we could land !253 too, for instance. But eh, fine, let's just call this the release.

@jdforrester jdforrester merged commit 0bd528d into master Nov 1, 2024
3 checks passed
@jdforrester jdforrester deleted the require18 branch November 1, 2024 14:39
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.

3 participants