Who patches Node.js after you deploy?
Your deployment is green and your Next.js app serves traffic. A day later, Node.js ships a security patch. Can your hosting provider tell you which version is running and who will update it? The 11 November releases are a good time to ask, especially if your app and its background jobs run in different places.
- Author
- Intercube
- Published
- Reading time
- 4 min read
01
The November patches are available
On 11 November the Node.js project released 22.23.5, 24.22.3 and 26.13.1. The project rated the most serious fixes high severity across all three lines. The release notes cover issues in HTTP/2 and TLS, among other components. Use the fixed patch for the supported line you already run. You can plan a major version upgrade separately.
If a reverse proxy handles connections from the internet, ask where HTTP/2 or TLS is used between the proxy, the app and other services. That tells you which traffic paths to test. The runtime update is still the step that delivers the fixes.
02
A green build tells you very little here
Take a Next.js storefront with a worker that sends order confirmations. The storefront can be redeployed from a patched image while the worker keeps running on an older one. Updating the Node.js version in CI will not change either service until the deployed runtime changes.
Ask for the running Node.js version of each service and where that version comes from. For a container, the answer should identify the deployed image. For a process on a managed server, it should identify the runtime the service uses. This is how you find the worker that needs a separate restart or release.
03
What you should see after the patch
For the storefront, load a representative page and place a test order in staging. Check that the worker processes it and the confirmation lands where expected. Once the patched release is live, compare error and queue behaviour with a normal period and confirm the runtime version in both processes.
If the patch follows unusual production errors or unexpected restarts, keep the earlier logs and investigate them through your incident process. The rollout and that investigation answer different questions. A patched process can still have logs worth reviewing from before the update.
04
What Intercube can take over
On Intercube managed hosting, our engineers operate the server runtime and help your team plan releases around it. If you own a container image, we agree who updates it and how the new image reaches every service. Your developers bring the application checks, such as an order flow that depends on a worker.
If production depends on a VPS maintained by whoever set it up, we can help move the app and workers onto a managed environment. We can prepare that environment and rehearse the release with your team. Migration to Intercube managed hosting is included at no additional cost.
Five questions for your host
- Which Node.js version is serving requests?
- Does the worker use the same runtime?
- Who updates the image or server runtime?
- How do we verify the new version after rollout?
- Who checks the application if errors rise?