Skip to content

Notifinho v2.5.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Jul 01:35
· 39 commits to main since this release
v2.5.3
ebbb47b
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.3 release notes

Released 27 July 2026.

Notifinho v2.5.3 is a schema-compatible corrective release for Synology input
selection, UniFi Protect webhook compatibility, and repository-independent
notification icons.

Synology

  • Synology is available through both SMTP and HTTP.
  • Existing Synology routes without input_type continue to infer SMTP.
  • Existing DSM email and authenticated webhook parsing is retained.

UniFi Protect

  • Valid Alarm Manager envelopes are accepted when outer alarm_id is absent.
  • timestamp remains required.
  • alarm must remain a dictionary.
  • Recognized nested shape and list validation remain enforced.
  • Missing optional alarm_id becomes an empty metadata value.

Self-contained notification icons

  • Discord and Microsoft Teams icons are loaded from the Docker image.
  • Discord uploads the exact selected root or padded asset as an attachment.
  • Microsoft Teams embeds the packaged icon as a Base64 data URI.
  • Release images no longer require public GitHub raw-content availability.
  • NOTIFINHO_ICON_BASE_URL and its build argument are removed.
  • NOTIFINHO_ICON_DIR is the local-directory override.
  • NOTIFINHO_DISCORD_ICON_DIR remains a compatible Discord fallback.

Upgrade

  1. Back up matched config, state, and secret directories.
  2. Pull fortpt/notifinho:2.5.3.
  3. Change only the image tag.
  4. Start Notifinho and confirm schema 8.
  5. Confirm Synology shows SMTP and HTTP.
  6. Send real Protect, Discord, and Teams tests.
  7. Complete docs/v2.5.3-acceptance-checklist.md.

HTTP and HTTPS access

Session, listener, reverse-proxy, and cookie behavior are unchanged.

Direct managed-mount deployment

Managed NFS/SMB behavior is unchanged.

Compatibility and rollback

Schema 8 remains unchanged and platform_database_v1 remains unchanged. No database
migration runs. The normalized config.yaml bootstrap structure is unchanged. After stopping v2.5.3, direct rollback to v2.5.2 is supported.
Keep the matched pre-upgrade backup until acceptance passes.

Assets 2
Loading