3 Commits
Author SHA1 Message Date
flan dc427c1fcb docs: Use a plain semver line for fork releases
CI / Check / HACS (push) Failing after 1m37s
CI / Test / Unit (push) Successful in 2m37s
CI / Test / Dist / Firefox (push) Successful in 1m44s
CI / Test / Dist / WebKit (push) Successful in 1m10s
Manage labels / Labeler (push) Successful in 19s
CI / Test / Browser / Firefox (push) Successful in 5m25s
CI / Check / Code (push) Successful in 2m46s
CI / Test / Dist / Chromium (push) Successful in 1m7s
CI / Test / Browser / Chromium (push) Successful in 4m39s
CI / Build (push) Failing after 42s
CI / Test / Browser / WebKit (push) Successful in 3m36s
Semantic Release / get-next-version (push) Successful in 51s
Semantic Release / release (push) Skipped
2026-09-04 18:03:37 +00:00
flan b57fd0675a docs: Add fork notes, changelog and notice 2026-09-04 17:59:21 +00:00
flan 88e1fba401 feat: Add cameras[].media.severities to filter review media by severity
Review queries were issued without a severity filter, so the thumbnail
bar, gallery and timeline showed every Frigate review item -- alerts and
detections alike -- regardless of what a camera is configured to alert
on. Severity could only be narrowed interactively, in the media filter
drawer, and that choice did not persist.

`media.severities` resolves into the default query the same way
`media.reviewed` does, and is overridden by an explicit severity filter
so the media filter drawer keeps working. Unset means all severities, so
existing behaviour is unchanged.

    cameras:
      - camera_entity: camera.office
        media:
          severities:
            - high
2026-09-04 17:56:20 +00:00