Skip to content

Notifinho v2.3.6

Choose a tag to compare

View all tags
@FortPT FortPT released this 23 Jul 23:32
· 47 commits to main since this release
v2.3.6
9c2c118
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.6 release notes

Released 24 July 2026.

v2.3.6 corrects the visual scope of the v2.3.5 source-icon change and replaces
the temporary Redfish artwork with the official DMTF Redfish identity. Platform
schema 6 and the unified config.yaml model remain unchanged.

Fixed

  • Restored every normal Overview source icon to the pre-v2.3.5 48 px size.
  • Kept enlargement limited to the requested Notifinho fallback, Dell iDRAC,
    UniFi Network, UniFi Protect, QNAP, and Synology identities.
  • Restored the normal Overview source-card height and column proportions so
    unrelated sources no longer consume additional space.
  • Changed the redfish source to the official DMTF Redfish logo.
  • Kept restful and rest_api aliases on the neutral REST API icon.
  • Retained the v2.3.5 body-free inactive-source removal endpoint.

Redfish asset

The release preparation retrieves the logo from DMTF's official Redfish site:

https://redfish.dmtf.org/sites/default/files/DMTF_Redfish_logo_R.jpg

The downloaded file is committed into the release tag so production containers
do not make an external request at runtime.

HTTP and HTTPS access

v2.3.6 does not change the existing trusted-LAN HTTP or reverse-proxied HTTPS
session, cookie, or CSRF contract. The Redfish logo is served as a packaged
same-origin WebUI asset; the browser does not retrieve it from DMTF at runtime.

Direct managed-mount deployment

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

Upgrade

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

Compatibility and rollback

v2.3.6 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.

Assets 2
Loading