How auto install decides

For a specific entity's pending update, Update Manager checks, in this exact order:

1. Hard gates. Excluded entities and anything skipped via Home Assistant's own "Skip this version" never auto-install. Core, Supervisor, and OS start out excluded by default; remove them from that list to make them eligible like anything else.
2. A trusted voter's "healthy" vote on this exact jump wins outright, skipping the wait and the size toggle, even over someone else's problem report on the same jump.
3. Any problematic community vote blocks it (unless step 2 already overrode it): one vote from anyone is enough, no quorum needed.
4. Otherwise, your own size-based rules apply: waiting period elapsed, size toggle on, announce, then install.

A blocked update shows an "Auto-install held back" alert naming the trusted voter or reported count; the Community section on that dialog shows each reported reason. A vote (and this block) applies to the exact version jump, not any known issue along the way.

See also: Known limitations for what voting can and can't cover.