Skip to content

Notifinho v2.5.4

Choose a tag to compare

View all tags
@FortPT FortPT released this 27 Jul 09:59
· 38 commits to main since this release
v2.5.4
c5959c6
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.4 release notes

Released 27 July 2026.

Notifinho v2.5.4 is a production corrective release for Discord packaged card
icons and persistent destination test health.

Discord packaged icons

The v2.5.3 image contained every mapped icon, but the v2 platform Discord
adapter sent the formatter payload as JSON and did not invoke the packaged-file
upload path. Discord therefore received the internal notifinho-asset://...
reference and rendered a broken image.

v2.5.4:

  • resolves the exact root or padded packaged PNG selected by the formatter;
  • sends the Components V2 payload as multipart/form-data;
  • references the file through attachment://filename;
  • requests wait=true from Discord;
  • verifies that the returned message contains the uploaded attachment and that
    the Thumbnail media links to it;
  • fails closed with a safe error if the icon is unavailable or Discord does not
    retain the association.

Destination health

Destination tests now persist these safe operational fields:

  • last_test_at;
  • last_test_outcome;
  • last_test_response_status;
  • last_test_error_code;
  • last_test_safe_error.

Destination cards show the safe failure reason. Routing Flow marks the
Destination node and its incoming arrow as failed after an unsuccessful test.
A successful retest immediately restores the healthy state. The result remains
available after browser refresh and container restart.

Schema migration

v2.5.4 advances the SQLite schema from 8 to 9. Migration 9 adds nullable test
health columns to destinations; existing destinations and routes are not
rewritten. The configuration model remains platform_database_v1.

Notifinho automatically creates a schema-8 database backup before migration.
Rollback to v2.5.3 requires stopping v2.5.4 and restoring that matching backup,
because v2.5.3 rejects a schema-9 database.

Upgrade

  1. Back up the matched config, state, and secret mounts.
  2. Deploy fortpt/notifinho:2.5.4 without changing volumes or credentials.
  3. Confirm the automatic schema-8 backup exists.
  4. Confirm the application reports version 2.5.4 and schema 9.
  5. Run a real Discord test for a padded source such as Xen Orchestra.
  6. Confirm the card contains the source icon instead of a broken placeholder.
  7. Run a failed destination test and confirm Routing Flow turns red and displays
    the safe reason.
  8. Correct the destination and retest; confirm Routing Flow returns green.
  9. Run one Microsoft Teams test and verify the packaged Base64 icon still works.

HTTP and HTTPS access

Listener, reverse-proxy, session, CSRF, cookie, and TLS behavior are unchanged
in v2.5.4. Existing HTTP or HTTPS deployment settings do not require changes.

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.4 upgrades the platform database from Schema 8 to Schema 9.
Migration 9 adds nullable destination test-health columns only. The
platform_database_v1 configuration model and config.yaml structure remain
unchanged.

Before migration, Notifinho creates a schema-8 backup in the state
schema-backups directory. Rolling back to v2.5.3 requires stopping v2.5.4 and
restoring the matching schema-8 database backup. Do not run v2.5.3 against a
schema-9 database.

Assets 2
Loading