Skip to content

EOL notification updated for node and chrome #22259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 21, 2025
Merged

EOL notification updated for node and chrome #22259

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e89cb8e
wip
cbehera-newrelic Nov 21, 2025
4cda6d4
EOL updated
cbehera-newrelic Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
211 changes: 4 additions & 207 deletions src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,212 +1,9 @@
---
title: "End of Life Announcement: For Chrome 134 and Node.js 16 runtime for synthetics"
subject: "On February 9, 2026, New Relic will upgrade synthetics runtime to Chrome 140 and Node.js 22, ending support for Chrome 134 and Node.js 16 runtimes."
title: "End of Life announcement for Node.js 16 and Chrome 134 runtimes used in synthetic monitors: Update Forthcoming"
subject: "Updated communication regarding Chrome 134 and Node.js 16 synthetics runtime support will be published shortly. Please stand by for official details."

Check notice on line 3 in src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md#L3 

[Microsoft.Passive] 'be published' looks like passive voice.
Raw output 
{"message": "[Microsoft.Passive] 'be published' looks like passive voice.", "location": {"path": "src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md", "range": {"start": {"line": 3, "column": 101}}}, "severity": "INFO"}
publishDate: '2025-11-05'
eolEffectiveDate: '2026-02-09'
---

On **February 9, 2026**, New Relic will upgrade synthetics runtime environments, ending support for:
Regarding the recent End-of-Life announcement about ending our support for Chrome 134 and Node.js 16 synthetics runtimes, we will be publishing an updated comprehensive communication shortly. Please stand by for the official update.

* Chrome 134 browser runtime
* Node.js 16 runtime for both API and browser monitors

The following upgrades will be implemented:

* **Synthetics Node API runtime**: Upgraded to Node.js 22
* **Synthetics Node browser runtime**: Upgraded to Node.js 22
* **Chrome browser**: Upgraded to Chrome 140
* Release candidate version available via Docker image tags (rc1.x)

## What's changing?

The following monitor types will be affected by these changes:

* Scripted Browser
* Scripted API

**Note:** Moving to Chrome 140 automatically upgrades to Node.js 22.

## Transition timeline

### Public locations

* **Node API runtime**: Default remains Node.js 16 until February 8, 2026. On **February 9, 2026**, all monitors will be force upgraded to Node.js 22.

* **Node Browser runtime**: Default remains Chrome 134 for three months starting November 1, 2025. Force upgrade to Chrome 140 occurs on **February 9, 2026**.

### Private locations

* **Node API runtime**: The "latest" tag on `DESIRED_RUNTIMES` will point to Node.js 22 runtime starting **December 1, 2025**. Until then, "latest" points to Node.js 16 runtime.

* **Node Browser runtime**: The "latest" tag on `DESIRED_RUNTIMES` will point to Chrome 140 with Node.js 22 runtime starting **December 8, 2025**. Until then, "latest" points to Chrome 134 with Node.js 16 runtime.



## Changes during transition period

### For public browser monitors

In the creation/edit monitor screen, you'll see the ability to select Chrome browser versions:

* Chrome 134
* Chrome 140


### For other monitor types

Select the runtime in the Configure monitor screen.



## What you need to do during the transition period

1. Review and test your monitors using the new runtime options available in the monitor configuration screens.

2. Address Node.js 22 time out behavior: Node.js 22 has documented issues with time out behavior for resource handles. Review the [Node.js 22 release documentation](https://nodejs.org/en/blog/announcements/v22-release-announce) for details.

3. Ensure monitors don't time out with Node.js 22 before the transition date.

### Handle resource cleanup properly

Our analysis indicates that Node.js executes browser monitor scripts successfully but waits for open handles, eventually causing monitor time-outs. Ensure proper cleanup of resource handles.

**Example 1 - Stream cleanup:**

```javascript
let downloadStream = got.stream(fileDownloadUrl);
// Add cleanup in finally block
finally {
if (downloadStream) {
downloadStream.destroy();
}
}
```

**Example 2 - HTTPS request cleanup:**

```javascript
const req = https.request(options, (res) => {
try {
const cert = res.socket.getPeerCertificate();

if (cert && Object.keys(cert).length > 0) {
const validTo = cert.valid_to || cert.validTo;
console.log("Raw certificate valid_to:", validTo);
resolve({ validTo: validTo });
} else {
reject(new Error("Could not get certificate information"));
}
} catch (err) {
res.destroy();
if (res.socket) res.socket.destroy();
reject(err);
}
});
```

In the above example, `res.socket` is opening the socket and in the if condition we are not closing the socket. For above code, you can add cleanup functionality as follows:

```javascript
const req = https.request(options, (res) => {
try {
const cert = res.socket.getPeerCertificate();

// Always destroy the response and socket
const cleanup = () => {
try {
res.destroy();
if (res.socket && !res.socket.destroyed) {
res.socket.destroy();
}
} catch (e) {
console.log("Cleanup warning:", e.message);
}
};

if (cert && Object.keys(cert).length > 0) {
const validTo = cert.valid_to || cert.validTo;
console.log("Raw certificate valid_to:", validTo);
cleanup();
resolve({ validTo: validTo });
} else {
cleanup();
reject(new Error("Could not get certificate information"));
}
} catch (err) {
res.destroy();
if (res.socket) res.socket.destroy();
reject(err);
}
});
```

**Example 3 - Consume the data event:**

When using `http` or `https`, you must listen to the data event, as shown below. Otherwise, the HTTPS connection may remain open.

```javascript

const https = require('https');

https.get('https://example.com', (res) => {
console.log('Status Code:', res.statusCode);
// It is necessary to consume the response data
res.on('data', (d) => {
process.stdout.write(d);
});
}).on('error', (e) => {
console.error('Error:', e);
});

```


**Example 4 - Disable keep-alive:**

Set the `keepAlive` option to `false` to close HTTP connections after the request is complete.

```javascript

const https = require('https');
const { Agent } = require('https'); // or http for HTTP requests

const options = {
hostname: 'example.com',
path: '/',
method: 'GET',
agent: new Agent({ keepAlive: false }), // Disable Keep-Alive for this request
};

const req = https.request(options, (res) => {
console.log(`Status: ${res.statusCode}`);
res.on('data', (d) => {
process.stdout.write(d);
});
});

req.on('error', (e) => {
console.error(e);
});

req.end();

```


## Troubleshooting

### Monitor time-outs or failures after upgrade

* Check for usage of deprecated Node.js APIs that were removed or changed in Node.js 22
* Re-run monitors locally using Node.js 22 to reproduce and fix issues
* If failures persist only on browser monitors, verify Chrome 140-specific behavior and contact support

### Rollback options

* **Public locations**: Temporarily switch monitor runtime back to Chrome 134 during the transition window

## Additional resources

* [Synthetics runtime documentation](https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/using-monitors/new-runtime/)

* If you have questions or need assistance during this transition, please contact our [support team](https://support.newrelic.com/s/)
In the meantime, if you have already begun testing or upgrading your monitors to the new runtimes (Chrome 140 and Node.js 22) and encountered any specific issues, please let our support team know. It will help us better assist you with the upcoming runtime migration.

Check notice on line 9 in src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md#L9 

[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).
Raw output 
{"message": "[Microsoft.SentenceLength] Try to keep sentences short (\u003c 30 words).", "location": {"path": "src/content/eol/2025/11/eol-chrome-140-node-22-synthetics.md", "range": {"start": {"line": 9, "column": 1}}}, "severity": "INFO"}
Loading