chore(dep): Updated @newrelic/security-agent to v0.4.0

[sumitsuthar]

Description

• Updated @newrelic/security-agent to v0.4.0

v0.4.0 (2023-10-27)

Features

• Added event stats for RASP, IAST and exit events in healthcheck.

Miscellaneous chores

• Deps: Updated uuid to v9.0.1 and @aws-sdk/client-lambda to v3.405.0
• Upgraded axios to 1.6.0 to resolve CVE-2023-45857

Continuous integration

• Removed Node.js 14.x from CI.
• Added should_skip flag to skip CI based on label.

How to Test

npm run versioned:security

[codecov]

Codecov Report

Merging #1837 (846bc77) into main (8b4e963) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1837   +/-   ##
=======================================
  Coverage   96.83%   96.83%           
=======================================
  Files         200      200           
  Lines       39073    39073           
=======================================
  Hits        37838    37838           
  Misses       1235     1235           

Flag	Coverage Δ
integration-tests-16.x	78.94% <ø> (ø)
integration-tests-18.x	79.22% <ø> (ø)
integration-tests-20.x	79.23% <ø> (-0.02%)	⬇️
unit-tests-16.x	91.35% <ø> (ø)
unit-tests-18.x	91.33% <ø> (ø)
unit-tests-20.x	91.33% <ø> (ø)
versioned-tests-16.x	73.15% <ø> (-0.01%)	⬇️
versioned-tests-18.x	73.15% <ø> (-0.01%)	⬇️
versioned-tests-20.x	73.16% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[sumitsuthar]

Node Agent CI / versioned-external (16.x) (pull_request) is failing due to next@14.0.0, which doesn't support Node v16.x

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'next@14.0.0',
npm WARN EBADENGINE   required: { node: '>=18.17.0' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }

[DavidRigglemanININ]

Do you have any info on when a release might be cut with this fix? We are stuck with the axios security vulnerability in our service due to this issue and cannot fully resolve until this is released. Thanks!

[mrickard]

@DavidRigglemanININ We're prepping a release now. Thank you for your patience!

[mrickard]

@DavidRigglemanININ This is included with v11.5.0, which should be available now.