[nadaverell]

Adds the v1.15.0 entry to the What's New catalog. This replaces #1877, which was stacked on the closed #1876; the dialog landed on main in #1902 instead. scripts/check-whats-new.sh (#1908) refuses to release v1.15.0 without this entry, so this must merge before the tag.

Highlights

A full-width lead card, then a 2x2 grid. Each secondary card has its own icon color, so they read apart.

1. AI investigations that show their work (lead, no CTA; the investigations workspace redirects home in run modes that can't host local agents). This recaps the v1.14.1 rework (Findings as a story: placed Radar cards, typed next steps, one assessment per pane, prompt rewritten for it #1766, Findings: a card for every tool result, and citations that reach them #1802) on purpose: it's the first What's New dialog, and we want to put AI investigations in front of people. OpenCode (feat(ai): support OpenCode investigations #1265) is the new v1.15 part.
2. Full manifest diffs for Argo CD resources (feat(gitops): expand resource diffs with manifest tabs and Monaco views #1622)
3. Rightsizing and cost data in MCP: new agent tools, and risks lead before savings in the UI too (Prioritize rightsizing risks and clarify incomplete results #1820, feat(mcp): expose cost and rightsizing data through MCP #1723)
4. Deeper batch + AI/ML workloads support: Kueue, JobSet and Ray pages; Job and JobSet details show why a queued job has no Pods (feat(kueue): add Workload admission detail #1874, Add native Kueue LocalQueue and ClusterQueue details #1885, Show Kueue admission evidence in Job detail views #1900, Investigate JobSets through role status, member resources, and logs #1849, Add RayService serving and runtime revision detail #1893, Add RayCluster runtime health and owned Pod detail #1897)
5. Canary and blue-green in Topology (feat(topology): visualize canary/blue-green traffic in the resource graph #1626)

Also in this release

Eight one-liners, paired by length because the grid fills row by row: table sort memory (#1428), OCI Helm installs (#1815), expiring TLS certificates in Checks (#1829), Radar Desktop keeping preferences across restarts (#1907), Pod vs template in Issues (#1848), PVC usage availability (#1828), Strimzi and admission webhook failures in Issues (#1840, #1830), --listen-address (#1845).

Left out: security fixes, dependency bumps, refactors and CI, accessibility work (#1901, #1909), and narrow items (ALB action annotations, INSTALL_DIR). No usage-stats line is needed, because #1879's consent question already sits in this dialog.

UI changes beyond the catalog

• The heading names the release line (v1.15, via releaseLine), since patch releases show the same notes. The "You just updated from → to" line keeps exact versions.
• An optional tone on highlights colors the icon tile (violet, teal, emerald, indigo). It uses Radar's existing bg-X-500/10 text-X-600 dark:text-X-400 pattern, and was checked in light and dark themes.

Verification

• scripts/check-whats-new.sh v1.15.0 → found notes
• make tsc clean; What's New and usage-data tests: 39 passed
• Previewed live with VERSION=v1.15.0 make build, opening /?whats-new, with Opt-in anonymous usage stats #1879's consent question in place

The matching public changelog is skyhook-dev/marketing#312.

---

Note

Low Risk
Release-notes catalog and presentational What's New UI only; no auth, API, or data-handling changes.

Overview
Adds the v1.15.0 What's New catalog entry (five highlights with CTAs where appropriate, plus eight improvement one-liners) so check-whats-new can ship the tag.

The dialog heading now shows the minor release line via new releaseLine() (e.g. v1.15 instead of v1.15.0), while the upgrade subtitle still uses exact versions. Secondary highlight cards can set an optional tone (violet, teal, emerald, indigo) for distinct icon tiles; the lead card stays on the accent style.

Tests cover releaseLine and the preview dialog title expectation.

^{Reviewed by Cursor Bugbot for commit f0038c3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Add v1.15.0 highlights to the What's New catalog

📝 Documentation 🕐 Less than 10 minutes

AI Description

• Adds six v1.15.0 highlights, led by verifiable AI investigations.
• Lists eight additional improvements and links supported highlights to their product areas.
• Supplies required release metadata and icons for the What's New dialog.

Diagram

graph TD
  G["Release check"] --> C["v1.15 catalog"] --> S["Notes selector"] --> D["What's New dialog"] --> R["Feature routes"]
  V["Runtime version"] --> S

Loading

High-Level Assessment

Using the existing typed release-notes catalog is the optimal approach: it preserves current version selection, dialog rendering, CTA navigation, and release-gate validation. External markdown or a separate content service would add parsing or operational complexity without benefiting this static, release-bound content.

Files changed (1) +65 / -1

Documentation (1) +65 / -1

releaseNotes.tsAdd the v1.15.0 release notes catalog entry +65/-1

Add the v1.15.0 release notes catalog entry

• Adds six illustrated highlights and eight supporting improvements for v1.15.0. The entry includes the release URL and in-app calls to action for GitOps, Checks, Rightsizing, and Topology, while intentionally leaving unsupported destinations unlinked.

web/src/components/whats-new/releaseNotes.ts