[nadaverell]

Description

Starting with 1.18.1, users upgrading from before 1.18—or from 1.18.0 without having acknowledged its notes—see What's New when they land on Home. A new Log viewer improvements highlight groups stable reading position, text selection without auto-scroll, and container-start waiting/status handling at importance 4. Together with the four existing highlights, the displayed score is 27, above the existing threshold of 25.

The existing announcement logic, importance scores of the other highlights, and card ranking remain unchanged. Fresh installs remain silent, deep links retain the unread indicator, and acknowledging v1.18 prevents its notes from replaying on subsequent patches. The v1.18 minor-release entry also describes Trivy resource-table findings search, MCP runtime inventory, broader issue diagnostics, shared Pod resource-budget audits, and confirmed Helm upgrade sources with ArtifactHub discovery.

Type of change

• Bug fix (non-breaking change that fixes an issue)

How has this been tested?

• 58 focused What's New tests passed; they cover the shipped catalog crossing the existing threshold, upgrades to 1.18.0/1.18.1, fresh installs, and no replay after acknowledgement.
• make build (frontend type-check/build, embed, and Go binary).
• Seven browser-smoke scenarios passed against the built UI and fake-Kubernetes test server, covering local/browser-backed upgrades, acknowledgement followed by a patch, fresh install, deep link, cloud-hidden behavior, and skipped releases where older higher-scoring cards take priority. Version/seen state is controlled in browser routes.
• Visual-test: skipped; small release-note content change using the existing dialog. The fixture browser smoke verifies the rendered log-viewer card.

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• Added/updated unit tests

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

PR Summary by Qodo

Automatically announce Radar 1.18 What's New after upgrades

🐞 Bug fix 📝 Documentation 🕐 10-20 Minutes

AI Description

• Open v1.18 What's New on Home after upgrades, despite its highlights falling below the score
 threshold.
• Keep fresh installs quiet and acknowledged releases closed without changing highlight ranking.
• Clarify scan search and MCP inventory, and refresh the v1.18 improvement list.

Diagram

graph TD
  State["Install version"] --> Unread["Unread releases"] --> Notes["Shown notes"] --> Gate{"Flag or score?"} -->|Yes| Home{"On Home?"} -->|Yes| Dialog["What's New dialog"]
  Gate -->|No| Dot["Unread indicator"]
  Home -->|No| Dot

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Raise v1.18 highlight scores

• ➕ Uses the existing score threshold without a new release field.
• ➖ Misrepresents highlight importance and changes card ranking for users who skipped releases.

2. Special-case the v1.18 version

• ➕ Keeps the release-note schema unchanged.
• ➖ Couples announcement policy to a version check in the dialog logic.

Recommendation: Keep the PR's declarative autoOpen flag. It expresses the release-specific decision in the catalog while preserving score-based ranking and requiring the release to be both unread and displayed.

Files changed (4) +46 / -11

Bug fix (1) +4 / -3

WhatsNew.tsxAllow displayed releases to request automatic opening +4/-3

Allow displayed releases to request automatic opening

• Lets an unread release marked autoOpen open composed notes when that release is among the displayed versions. The existing score threshold remains an alternative trigger.

web/src/components/whats-new/WhatsNew.tsx

Tests (2) +31 / -0

WhatsNew.test.tsCover explicit v1.18 announcement eligibility +21/-0

Cover explicit v1.18 announcement eligibility

• Tests automatic opening below the score threshold for upgrades to v1.18.0 and v1.18.1. Also checks acknowledgement, fresh installs, unchanged scores, and exclusion beyond the three-release display window.

web/src/components/whats-new/WhatsNew.test.ts

WhatsNewDialog.test.tsxVerify v1.18 dialog acknowledgement on Home +10/-0

Verify v1.18 dialog acknowledgement on Home

• Integration tests confirm the shipped notes open after upgrades to v1.18.0 or v1.18.1. Closing the dialog records the running version and clears unread status.

web/src/components/whats-new/WhatsNewDialog.test.tsx

Documentation (1) +11 / -8

releaseNotes.tsMark v1.18 for announcement and refine release copy +11/-8

Mark v1.18 for announcement and refine release copy

• Adds an optional release-level autoOpen flag and enables it for v1.18 without altering importance scores. Revises descriptions to distinguish scan-report search from MCP runtime inventory, broadens issue-detection wording, and updates the improvement list.

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

[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 choose which labels appear on a finding, and whether they show icons or text

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗