Integration: Return of the "update all"

[JPM-git]

Category

• [ ] Backend/Integration
• [X] Frontend
• [ ] Documentation
• [ ] Bot
• [ ] Other

Checklist

• [X] This Feature Request only contain 1 request (if you have multiple open multiple feature requests).

The idea

Being able to upgrade all repository at once with one click, so this avoid opening multiple pop-ups to upgrade each component.

Implementation

There used to be a "update all" componente every since version before 1.0, now with the latest version i have to go to each component and open, select update, wait for the pop-ip to close, and do the same for all the rest.

[hacs-bot[bot]]

Make sure you have read the issue guidelines and that you filled out the entire template.

[ludeeus]

Due to a good amount of complaints from maintainers this will not be reimplemented.
Users would just click that, and therefore not see release notes (which contains breaking changes).
This resulted in stuff breaking.

[IronicBadger]

How about a checkbox style system to update multiple integrations at once? Manually updating 30+ integrations is incredibly tedious.

It is my problem if I update and break something without reading the changelog. Perhaps under an 'advanced mode' we could have this functionality back? I miss it dearly.

Let's also consider that as it stands the changelog is not front and center despite there being plenty of UI space available for it.

[etricky]

@ludeeus I fail to understand your logic on how not having the update all option will solve the problem of users not checking breaking changes. If users didn't saw the release notes before, they will continue not to see them even if they have to manually update each integration.

My suggestion is that all integrations must follow semantic versioning (major, minor, patch) which is followed by most software programs and any new major release does not get included in the update all option. If developers of integrations don't follow this rule for the versioning it will be their problem to solve as you would have given them a way to notify users of breaking changes. Since it is not that frequent to have major versions, most of the times, the update all option would be sufficient. Integrations with new major versions would be have to be updated manually which, at least, would signal users to check the release notes before doing the update.

This is just my suggestion, perhaps, there may be another way to accomplish this, but I sincerely believe that the update all option is something most users truly appreciate and miss as it greatly simplifies the update process. Please, reconsider having the update all option available again.

[boesing]

I think the main issue is, that maintainers mostly does not follow semver.
I would love to have an "update all" button, if all versions are bc safe, but actually most of the packages are not. I understand why this got removed.

Having a button which automatically updates inside a major version would be find, as there should be no bc breaks. It should just prevent me from upgrading to a new major version with possible bc breaks. Maybe, somewhen in the future, this functionality will be implemented. We'll see.

[timdonovanuk]

Having to manually click update on my 20+ integrations/frontend is not more likely to make me read the release notes.

Please reconsider adding this button.

[IronicBadger]

Any word from a dev? Having to click a dozen individual updates is silly.

[Mincka]

Silly proposal: would it be possible to create a custom_component that handles this with the HACS API?