Skip to content

Group pending updates by category on the updates page#52215

Open
MindFreeze wants to merge 8 commits into
devfrom
updates-grouped-by-category
Open

Group pending updates by category on the updates page#52215
MindFreeze wants to merge 8 commits into
devfrom
updates-grouped-by-category

Conversation

@MindFreeze
Copy link
Copy Markdown
Member

@MindFreeze MindFreeze commented May 26, 2026

Breaking change

Proposed change

Restructures the Settings → Updates page (/config/updates) to group pending updates into categorized cards, replacing the single flat "Installable" card:

  1. Home Assistant card at the top — Home Assistant Core / Operating System / Supervisor. No "Update all" (these need to be prioritized).
  2. One card per integration that has 2 or more pending updates (e.g., "ESPHome" if multiple ESPHome devices have updates). Each has an "Update all" button.
  3. Integrations card bundling single-instance integration updates. Has "Update all".
  4. Apps card bundling add-on updates. Has "Update all".
  5. The existing Not installable card stays unchanged below.

"Update all" makes one update.install service call with the group's entity IDs — no confirmation dialog, no backup flag.

Implements the design from the last comment of #29910.

cc @marcinbauer-ohf

Screenshots

These are mocked updates

image

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion: Update multiple update entities at once #29910
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to backend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • I have followed the perfect PR recommendations
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

To help with the load of incoming pull requests:

Comment thread src/panels/config/core/ha-config-section-updates.ts
@MindFreeze MindFreeze marked this pull request as ready for review May 26, 2026 13:58
Comment thread src/panels/config/core/ha-config-section-updates.ts
Comment thread src/panels/config/core/ha-config-section-updates.ts Outdated
Comment thread src/panels/config/core/ha-config-section-updates.ts
Comment thread src/panels/config/core/ha-config-section-updates.ts
Comment thread src/panels/config/core/ha-config-section-updates.ts Outdated
@home-assistant home-assistant Bot marked this pull request as draft May 27, 2026 07:52
@home-assistant
Copy link
Copy Markdown

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@MindFreeze MindFreeze marked this pull request as ready for review May 27, 2026 08:34
@home-assistant home-assistant Bot requested a review from wendevlin May 27, 2026 08:34
@marcinbauer-ohf
Copy link
Copy Markdown
Member

@MindFreeze can we remove the loading state of the "Update all" button? The ones for each item is enough.
CleanShot 2026-05-27 at 11 15 45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants