Hey all, With Node 14 going out of security suppo...
# pact-js
y
Hey all, With Node 14 going out of security support in 2 weeks, what are peoples current projects like in terms of updating? https://endoflife.date/nodejs • Is anyone still running node 12.x / 14.x apps or earlier ◦ How important are your libraries you depend on, supporting those? • As what point do maintainers stop supporting the runtimes? (maybe for your own projects, but this will be a wider question proposed to our javascript pact community)
t
Most libraries are staying in step with the node release cycle, I thought there was a note about this somewhere
y
thanks buddy, that was a good read.
🙌 1
so come eol of node 14 lts in a couple of weeks, we switch off node 14 ci, set the engines flag and do a major version bump, and build a nice compat matrix matching node release lts versions and show tests running against them is my tl;dr from that
t
Yep
That’s what I used to do when I maintained it
except for the compat matrix. I just put it in the changelog.
I think doing that kind of release means that you must have good changelogs - as in, each changed item is understandable to a user with no context of the internals, no empty release note releases, clear migration guidelines for breaking changes, etc.
One really nice feature of release please is that you can change the release notes for a PR after it has been merged, so you don’t have to be so draconian about commit messages in first-time contributor PRs. However, one downside is that it requires squash merges if you want to totally override the commit messages on the branch.
Also, I don’t run CI on node’s bleeding edge releases (the odd version numbers). This is because I found they produced too many broken builds.
@Yousaf Nabi (pactflow.io) - I reckon you’d like JSii’s approach to this problem:
y
Yeah the pact ruby standalone with my changes in won't execute under node 19 on windows for me, for nodeymcreasons. I personally LOVE that messaging though, will 110% take a look
t
nodeymcreasons
😂