Skip to content

Notifinho v2.5.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Jul 02:46
· 42 commits to main since this release
v2.5.2
3aa7b1f
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.5.2 release notes

Released 25 July 2026.

v2.5.2 completes the approved Routing Flow presentation and hardens notification icon delivery.

Routing Flow

  • Disabled flow uses a yellow typographic prohibition symbol aligned with the working arrow.
  • Destination cards show the configured destination name first.
  • The second line shows the output platform and configured channel, for example Discord · #idrac-alerts.
  • Source, route, connector, and destination health remain independently coloured.

Notification icons

  • Xen Orchestra, Grafana, TrueNAS, Portainer, Home Assistant, Supermicro, and Zabbix use padded Discord-specific images so their visible thumbnail artwork is smaller.
  • Microsoft Teams keeps the existing official asset sizing.
  • WebUI source artwork, outbound regular assets, and Discord variants are all copied into and verified inside the release image.
  • Published images use an immutable commit-addressed GitHub raw URL for outbound card artwork. NOTIFINHO_ICON_BASE_URL remains available for mirrors and branded clones.

Settings layout

The Settings page now uses the full available workspace width, aligning its
panels with the Overview page while preserving responsive integration cards
and section spacing.

Upgrade

  1. Back up the mounted config, state, and secret directories.
  2. Pull fortpt/notifinho:2.5.2.
  3. Change only the image tag in the existing Portainer stack and re-pull the image.
  4. Confirm schema 8, a clean startup, Routing Flow labels, and real Discord/Teams test cards.
  5. Complete docs/v2.5.2-acceptance-checklist.md.

HTTP and HTTPS access

Session and listener behaviour are unchanged. Direct HTTP is appropriate only on a trusted network. Public access must terminate TLS at a trusted reverse proxy and enable HTTPS enforcement and secure cookies.

Direct managed-mount deployment

Managed NFS/SMB behaviour is unchanged and remains opt-in through the existing deployment override.

Compatibility and rollback

The normalized config.yaml structure introduced in v2.5.0 remains unchanged in this release.

Schema 8 remains unchanged and no database migration runs. Schema remains 8 and no database migration runs. After stopping v2.5.2, a direct image rollback to v2.5.1 is supported. Keep the matched pre-upgrade backup until production acceptance passes.

Assets 2
Loading