4.0.0

[trentm]

Mainly this is a new 4.x major release stream to bump the minimum supported Node.js to allow us to modernize.
The new min support Node.js is v14.17.0.
We will maintain 3.x (in the "3.x" branch) for 6 months.

See the changelog (https://github.com/elastic/apm-agent-nodejs/blob/main/CHANGELOG.asciidoc#400---20230907) for a list of breaking changes. Our hope is that upgrading is not onerous at all -- assuming you are using a supported Node.js version. There is an upgrade guide as well (link coming once we have a docs build of that).

checklist

• merge chore: improve release tagging to support pre-releases #3612 first
• possibly do a 4.0.0-rc.1 release (it should not be marked as latest in npm)

[david-luna]

holding the approval to avoid merging before #3612

[trentm]

• possibly do a 4.0.0-rc.1 release (it should not be marked as latest in npm)

This didn't work. I'll open a separate bug to handle the npm publish tagging correctly for pre-releases. I got it wrong trying to interpret whether npm publish uses a "latest" tag for pre-releases from experimentation. My experimentation was with the https://www.npmjs.com/package/@trentm/npmplay package.

[trentm]

• npm package is published
• GH release (with the table of Lambda layers) is here: https://github.com/elastic/apm-agent-nodejs/releases/tag/v4.0.0
• Release notes are here: https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.0.0 (there is still a docs build in progress)
• Migration/Upgrade guide is here: https://www.elastic.co/guide/en/apm/agent/nodejs/current/upgrade-to-v4.html