[nadaverell]

Adds the in-app What's New entry for Radar v1.18.0, covering the user-facing changes merged since v1.17.0.

Four highlight cards cover CVE investigation (the lead, importance 8), MCP guidance and controls, richer change evidence, and workload blockers (importance 5 each). The CVE highlight combines Trivy search with PR #2265’s MCP inventory of runtime versions declared by running images, including supported fixed-release comparisons and explicit unknowns. Image declarations do not verify remediation. Change evidence groups broader spec diffs, policy and label changes, Secret rotations and incomplete-history notices. Workload blockers group policy and admission failures, mixed Service backends, volume conflicts, storage rollout deadlocks and CronJob scheduling failures. The total score of 23 stays below the automatic-open threshold of 25 for upgrades from v1.17.

Eight smaller improvements cover log reading, saved column order, native sidecars, drain outcomes, incomplete issue checks, Helm chart sources, Prometheus reconnection and missing Argo resources.

Preview URLs now accept ?whats-new=v1.18 as well as v1.18.0. Bare ?whats-new previews the newest authored release, allowing development builds to preview v1.18 independently of their Git-derived build version. Previews do not mark notes as seen.

Validation:

• make tsc
• cd web && ../node_modules/.bin/vitest run src/components/whats-new — 54 tests passed
• bash scripts/check-whats-new.sh v1.18.0
• make build
• Visual-test: skipped; existing dialog copy and preview selection logic, no layout changes.

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

PR Summary by Qodo

Add Radar v1.18.0 What's New release notes

📝 Documentation 🕐 Less than 10 minutes

AI Description

• Add five v1.18.0 highlight cards covering investigations, CVE search, workload blockers, columns,
 and drains.
• Summarize eight smaller improvements and link relevant cards to their in-app pages.

Diagram

graph TD
  A["v1.18.0 notes"] --> B["Release composer"] --> C["What's New dialog"] --> D["Feature pages"]

Loading

High-Level Assessment

Adding an entry to the existing release-notes catalog is the right approach: the composer, dialog, and release gate already consume it. A separate rendering path would duplicate established behavior without a clear benefit.

Files changed (1) +58 / -1

Documentation (1) +58 / -1

releaseNotes.tsAdd the v1.18.0 What's New catalog entry +58/-1

Add the v1.18.0 What's New catalog entry

• Adds five scored highlight cards, including a longer lead description for stale Secret and ConfigMap environment values, and eight short improvement lines. Three cards provide in-app links to Issues, Pods, or Nodes; new icons support the Secret and CVE search cards.

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

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.

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

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Issues promise links they do not show ✓ Resolved

Description

The workload-rejection-evidence card says the Issues page links quotas, LimitRanges and webhooks
for rejected Pods, but admission-blocker correlation is attached only by the MCP path and the API
type marks related correlation fields MCP-only. Users following the card's /issues CTA therefore
see NetworkPolicy context but not the promised admission links.

Code

web/src/components/whats-new/releaseNotes.ts[R72-75]

+        description: 'Issues flag deny-all NetworkPolicies affecting Services and link the quota, LimitRange or webhook that rejected a workload’s Pods.',
+        importance: 6,
+        path: '/issues',
+        cta: 'Open Issues',

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The workload-rejection release note claims that the web Issues page links quotas, LimitRanges, and webhooks that rejected workload Pods, but those admission-blocker links are currently produced only through MCP correlation. The card's `/issues` CTA directs users to a surface that does not provide the promised links.
## Fix Focus Areas
- web/src/components/whats-new/releaseNotes.ts[72-75]
- packages/k8s-ui/src/components/issues/types.ts[300-313]
- internal/mcp/issue_correlation.go[145-146]
## Recommended Fix
Rewrite the description to describe only the evidence rendered by the web Issues page, such as deny-all NetworkPolicies and their affected Services/workloads, or add the missing admission-blocker data to the web API and UI before advertising those links.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗