Skip to content
Back to feed

November 4, 2026 · Google CloudBreaking

Action needed

Edge Microgateway 3.3.12 drops Node.js 20 and removes npm from Docker image

Removed support for Node.js 20 from Edge Microgateway. Use Node.js 22, 24, or 26 instead.

Edge Microgateway 3.3.12 supports only Node.js 22, 24, and 26. Support for Node.js 26 is new in this release. Before you upgrade an npm installation of Edge Microgateway to 3.3.12, upgrade the Node.js runtime on each host to version 22, 24, or 26. The 3.3.12 Docker image is built on Node.js 24, so Docker deployments need no action for this change. For supported versions, see Supported software and supported versions.

Removed the npm and npx command-line tools from the Edge Microgateway Docker image. Install custom plugin dependencies before you add the plugins to the container.

Starting with version 3.3.12, the Edge Microgateway Docker image doesn't include npm or npx, and commands that run either tool inside the container fail. The change doesn't affect how Edge Microgateway runs. If your custom plugins have npm dependencies, run npm install in each plugin directory before you add the plugins to the container, so that each plugin's node_modules directory is included. For the steps, see Adding a custom plugin. This change doesn't affect npm installations of Edge Microgateway.

Text from the Google Cloud release notes, licensed under CC BY 4.0. Source: Google Cloud release notes.

Latest Apigee Edge for Public Cloud changes

All Apigee Edge for Public Cloud changes