kde-neon: switch to resolute base, then disable (broken)

[igorpecovnik]

What

KDE Neon was moved off Ubuntu 24.04 (noble) onto 26.04 LTS (resolute), but it does not work on that base — neon's testing archive (archive.neon.kde.org/testing) does not publish against resolute. So the desktop is disabled until upstream catches up.

Changes

• tools/modules/desktops/yaml/kde-neon.yaml
  • release noble: → resolute:
  • status: supported → status: unsupported
• tests/KDEN01.conf
  • RELEASE noble → resolute
  • ENABLED=true → ENABLED=false (matches the deepin/budgie disabled-test convention), with a comment explaining why

Re-enabling

Flip ENABLED back to true and restore status: supported once the neon repo carries resolute/26.04 packages.

[coderabbitai]

Warning

Review limit reached

@igorpecovnik, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: aae22ec2-f763-4fdf-8dd5-db319dc0c739

📥 Commits

Reviewing files that changed from the base of the PR and between 1f8638e and bad63aa.

📒 Files selected for processing (2)

• tests/KDEN01.conf
• tools/modules/desktops/yaml/kde-neon.yaml

Walkthrough

The KDE Neon test configuration and desktop release mapping were updated to replace the Ubuntu codename noble with resolute. No other configuration values or test logic changed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title matches the main change: moving KDE Neon to the resolute base, with a note about temporary disablement.
Description check	✅ Passed	The description is clearly about the KDE Neon resolute-base move and temporary disablement, matching the changeset.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kde-neon-resolute-base

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}