Announce EoL date for legacy JS SDKs (#606)

Author: adams85

website/docs/news.mdx

@@ -44,7 +44,7 @@ The new SDK combines and, thus, supersedes these SDKs:
 * [ConfigCat SDK for Chromium Extensions](https://github.com/configcat/js-chromium-extension-sdk)
 
 The legacy SDKs remain available for use but won't receive new features and improvements any more. They will continue
-getting security updates for a limited time, until they're eventually phased out.
+getting security updates until official support ends on August 31, 2026.
 
 The new SDK maintains strong backward compatibility, so in most cases migration is simple and straightforward.
 For details, see the "Migration to the new SDK" section in the SDK references linked above.

website/docs/sdk-reference/js-ssr.mdx

@@ -17,7 +17,9 @@ export const JavaScriptSSRSchema = require('@site/src/schema-markup/sdk-referenc
 [![Known Vulnerabilities](https://snyk.io/test/github/configcat/js-ssr-sdk/badge.svg?targetFile=package.json)](https://snyk.io/test/github/configcat/js-ssr-sdk?targetFile=package.json)
 
 :::caution
-This SDK is no longer maintained as it has been superseded by the new [Browser (JavaScript) SDK](../js/browser).
+This SDK is superseded by the new [Browser (JavaScript) SDK](../js/browser).
+
+This legacy SDK is in maintenance mode now, it will receive only critical security patches until **official support ends on August 31, 2026**.
 
 For guidance on migration, see [this section](#migration-to-the-new-sdk).
 :::

website/docs/sdk-reference/js.mdx

@@ -21,7 +21,9 @@ export const JavaScriptSchema = require('@site/src/schema-markup/sdk-reference/j
 [![JSDELIVR](https://data.jsdelivr.com/v1/package/npm/configcat-js/badge)](https://www.jsdelivr.com/package/npm/configcat-js)
 
 :::caution
-This SDK is no longer maintained as it has been superseded by the new [Browser (JavaScript) SDK](../js/browser).
+This SDK is superseded by the new [Browser (JavaScript) SDK](../js/browser).
+
+This legacy SDK is in maintenance mode now, it will receive only critical security patches until **official support ends on August 31, 2026**.
 
 For guidance on migration, see [this section](#migration-to-the-new-sdk).
 :::

website/docs/sdk-reference/node.mdx

@@ -19,7 +19,9 @@ export const NodeSchema = require('@site/src/schema-markup/sdk-reference/node.js
 [![Node.JS](https://img.shields.io/node/v/configcat-node)](https://img.shields.io/node/v/configcat-node)
 
 :::caution
-This SDK is no longer maintained as it has been superseded by the new [Node.js SDK](../js/node).
+This SDK is superseded by the new [Node.js SDK](../js/node).
+
+This legacy SDK is in maintenance mode now, it will receive only critical security patches until **official support ends on August 31, 2026**.
 
 For guidance on migration, see [this section](#migration-to-the-new-sdk).
 :::

website/versioned_docs/version-V1/news.mdx

@@ -44,7 +44,7 @@ The new SDK combines and, thus, supersedes these SDKs:
 * [ConfigCat SDK for Chromium Extensions](https://github.com/configcat/js-chromium-extension-sdk)
 
 The legacy SDKs remain available for use but won't receive new features and improvements any more. They will continue
-getting security updates for a limited time, until they're eventually phased out.
+getting security updates until official support ends on August 31, 2026.
 
 The new SDK maintains strong backward compatibility, so in most cases migration is simple and straightforward.
 For details, see the "Migration to the new SDK" section in the SDK references linked above.