Skip to content

Notifinho v2.3.7

Choose a tag to compare

View all tags
@FortPT FortPT released this 24 Jul 00:00
· 46 commits to main since this release
v2.3.7
b978b59
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Notifinho v2.3.7 release notes

Released 24 July 2026.

v2.3.7 supersedes the merged but unpublished v2.3.6 visual correction. It keeps
all WebUI Overview source cards and icon layout boxes identical to Home
Assistant while scaling only selected artwork inside those fixed boxes.
Platform schema 6 and the unified config.yaml model remain unchanged.

Fixed

  • Every Overview source card now uses the same row dimensions as Home Assistant.
  • Every desktop source icon keeps a 48 × 48 px layout box.
  • Every mobile source icon keeps a 44 × 44 px layout box.
  • Notifinho, Dell iDRAC, UniFi Network, UniFi Protect, QNAP, and Synology artwork
    is enlarged only with CSS transforms; the transform does not alter layout.
  • Redfish keeps the official packaged DMTF Redfish image at the normal Overview
    box size.
  • The v2.3.5 body-free inactive-source removal endpoint remains unchanged.
  • Notification payloads, source formatters, destination icons, and delivery
    rendering are not changed by this release.

HTTP and HTTPS access

v2.3.7 does not change the trusted-LAN HTTP or reverse-proxied HTTPS session,
cookie, CSRF, or same-origin asset contract.

Direct managed-mount deployment

v2.3.7 does not change the managed NFS/SMB backup override, mount behaviour, or
capability requirements. Continue using the existing production and
managed-backup Compose files.

Upgrade

  1. Back up the complete configuration, state, logs, and secrets mounts.
  2. Pull fortpt/notifinho:2.3.7.
  3. Redeploy with the existing Compose configuration.
  4. Force-refresh the WebUI once.
  5. Complete the v2.3.7 acceptance checklist.

Compatibility and rollback

v2.3.7 does not change the database or configuration schema. A direct rollback
to v2.3.5 remains supported when configuration and state are retained as one
matched set. v2.3.6 was not published and is not required as an intermediate
upgrade.

Assets 2
Loading