fix(frontend): Windows 10 lifecycle text/badge were stale (dated Oct 2025, now Aug 2026)

Homepage's featured card said "Security support until October 2025" --
that date has already passed, so it read as a future deadline that
wasn't. Updated to reflect actual status (mainstream support ended,
consumer ESU runs through Oct 2026) -- kept tight to match the other
three cards' description length so the grid stays even (the first
draft ran long enough to wrap to 3 lines and grow that one card's
height past its siblings).

Also found products.json still tagged both Windows 10 22H2 variants
(2618, 2378) as "EOL SOON" -- inconsistent with the homepage's own
"EOL"/"END OF LIFE" badge for the same product, and equally stale
for the same reason. products.json's badge field renders verbatim
on the product detail page, so this was live and user-facing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Shekhar Vaidya 2026-08-17 23:28:21 +05:30
parent f6659fcc42
commit d562bf8d0e
2 changed files with 3 additions and 3 deletions

View file

@ -12,7 +12,7 @@
},
"2378": {
"name": "Windows 10 22H2 Home China (19045.2006)",
"badge": "EOL SOON",
"badge": "EOL",
"archs": [
"x64"
],
@ -22,7 +22,7 @@
},
"2618": {
"name": "Windows 10 22H2 v1 (19045.2965)",
"badge": "EOL SOON",
"badge": "EOL",
"archs": [
"x64",
"x86"

View file

@ -35,7 +35,7 @@ const featured = [
name: 'Windows 10',
version: '22H2',
build: '19045.2965',
description: 'The final Windows 10 feature update. Security support until October 2025.',
description: 'The final Windows 10 feature update. Support ended Oct 2025; ESU through Oct 2026.',
badge: 'eol' as const,
archs: ['x64', 'x86'],
},