Cloud Manager pipeline fails at npm audit step with ENOAUDIT and endpoint retirement notice
This article describes how to resolve Cloud Manager pipeline failures at the npm audit step caused by the use of a deprecated npm audit endpoint.
Description description
Environment
- Adobe Experience Manager Cloud Manager (all versions)
Symptoms
- The Cloud Manager pipeline fails during the npm audit step, before the Maven build starts.
- Errors observed include:
npm notice This endpoint is being retired. Use the bulk advisory endpoint instead.npm ERR! code ENOAUDITnpm ERR! audit Your configured registry (https://registry.npmjs.org/) may not support audit requests, or the audit endpoint may be temporarily unavailable.- The clone and changelog steps succeed, but the npm audit step fails, preventing the pipeline from proceeding to the Maven build.
- Running the same npm audit command locally with the same commit and Node/npm versions succeeds and doesn’t show the deprecation notice.
- The error isn’t reproducible locally, regardless of the presence of
node_modulesor the Node version used.
Cause
The Cloud Manager pipeline’s built-in npm audit step runs with the default Node 14 / npm 6 runtime, which uses a deprecated audit endpoint. This endpoint has been retired, causing the audit to fail with ENOAUDIT, even if the same command succeeds locally on newer Node/npm versions. Setting the pipeline variable NODE_VERSION=18 ensures the audit step uses a supported endpoint.
Resolution resolution
Follow the steps below to resolve the issue:
- In Cloud Manager, add the pipeline variable
NODE_VERSION=18to your pipeline configuration. - Rerun the pipeline.
- Confirm that the npm audit step now completes successfully and the pipeline proceeds to the Maven build.
Note: Updating Node.js only in the repository (For example: via .nvmrc or package.json engines) doesn’t affect the Node version used by the built-in audit step in the Cloud Manager front-end pipeline container.