Skip to content

Notifinho v2.5.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Jul 13:34
· 36 commits to main since this release
v2.5.5
99524b5
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.5 release notes

Released 27 July 2026.

Notifinho v2.5.5 is a production corrective release for Microsoft Teams
destination tests and source icons.

Microsoft Teams delivery

The v2.5.4 generic destination-test card embedded the 30,813-byte Notifinho
PNG as a Base64 data URI. The resulting JSON payload was 43,034 bytes, above
Microsoft Teams' documented 28 KiB webhook-message limit. A Teams Workflow
could return HTTP 202 Accepted before its channel-post action later rejected
the oversized message, while the WebUI incorrectly said it was delivered.

v2.5.5:

  • uses public HTTPS image URLs for Microsoft Teams source icons;
  • keeps Discord on packaged multipart image attachments;
  • checks the serialized Teams card before every legacy or platform send;
  • rejects a payload larger than 28 KiB without making a webhook request;
  • records the safe teams_payload_too_large error for destination tests;
  • identifies HTTP 202 as accepted, with delivery not yet confirmed;
  • preserves the HPE iLO image and all existing source-specific card layouts.

Release images pin NOTIFINHO_TEAMS_ICON_BASE_URL to the immutable tagged
commit. Operators may override that environment variable with another
credential-free public HTTPS directory containing the same mapped filenames.

Schema and configuration

No database migration is required. v2.5.5 continues to use schema 9 and the
platform_database_v1 configuration model. Existing config.yaml, users,
destinations, routes, secrets, preferences, backups, and history remain
compatible.

Upgrade

  1. Back up the matched config, state, and secret mounts.
  2. Deploy fortpt/notifinho:2.5.5 without changing volumes or credentials.
  3. Confirm the application reports version 2.5.5 and schema 9.
  4. Send a generic Notifinho test to Microsoft Teams.
  5. Confirm the WebUI reports HTTP 202 as accepted, not delivered.
  6. Confirm the test card appears in the configured Teams channel.
  7. Send an HPE iLO source-aware test and confirm the HPE iLO image appears.
  8. Send one Discord test and confirm its packaged source image still appears.
  9. Confirm restart count remains zero and no delivery traceback is logged.

HTTP and HTTPS access

Listener, reverse-proxy, session, CSRF, cookie, and TLS behavior are unchanged
in v2.5.5. Existing HTTP or HTTPS deployment settings do not require changes.
Teams icon URLs must remain publicly retrievable over HTTPS because Microsoft
Teams fetches them independently of the Notifinho container.

Direct managed-mount deployment

Managed NFS and SMB backup mounts are unchanged. Existing direct and
Portainer-managed deployments must retain their current volume mappings,
mount options, credentials, and backup configuration.

Compatibility and rollback

Notifinho v2.5.5 retains schema 9, the platform_database_v1 model, and the
v2.5.4 database structure. No schema backup is created specifically for this
upgrade.

Rollback to v2.5.4 is schema-compatible, but v2.5.4 reintroduces the oversized
generic Teams test and Base64 source-image behavior. Stop the container before
changing image tags. Keep the normal matched config, state, and secrets backup
until real Teams and Discord acceptance checks pass.

Assets 2
Loading