Skip to content

Notifinho v2.5.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Jul 00:04
· 43 commits to main since this release
v2.5.1
89c03d1
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.1 release notes

Released 25 July 2026.

v2.5.1 makes generic routes true fallbacks and normalizes the WebUI around the
three supported event inputs: SMTP, HTTP, and Redfish.

Fallback-only routing

  • Dedicated integration routes are evaluated before wildcard routes.
  • Wildcard routes run only when no dedicated route matches.
  • Multiple matching routes to the same destination produce one delivery using
    the highest-priority route.
  • Route filters support include and exclude lists for hosts/devices, events,
    severities, and statuses.
  • Existing Xen Orchestra success/skipped/failure switches are migrated once into
    route status filters. Xen Orchestra integration settings retain only the
    formatter option for job and run IDs.

WebUI normalization

  • Sources show only SMTP, HTTP, and Redfish input badges.
  • Redundant text such as “events received through HTTP” is removed.
  • Destination Enabled/Disabled and Shared/Private states are clickable.
  • The positive Credentials set badge is removed; only missing credentials and
    destination test outcomes are shown.
  • Applications is renamed to Event API tokens and explains that tokens are used
    only by external applications posting to /api/v2/events.
  • Token source scopes are selected from the complete integration catalogue, with
    optional custom source identifiers.
  • Integration behavior cards use consistent spacing and summaries.
  • Overview flow diagnostics are independent: source/input, route, and destination
    cards each report their own state. Green arrows mean working, yellow prohibition
    symbols mean disabled, and red X symbols mean unavailable or invalid.
  • The source-side status line follows the selected input instead of the destination.
  • The Inputs page exposes only the normalized SMTP, HTTP, and Redfish names.
  • Disabling the logical Redfish input acknowledges subscribed controllers without routing events, avoiding retry storms while the input is intentionally paused.
  • Regional and integration settings panels have a clear vertical gap.

Upgrade

  1. Back up the matched config, state, and secret directories.
  2. Validate the release candidate on VM-09 with a copied production snapshot.
  3. Deploy fortpt/notifinho:2.5.1 through the existing Portainer stack.
  4. Confirm schema 8, resource counts, fallback routing, destination controls,
    Event API token scopes, and real Discord/Teams delivery.
  5. Complete docs/v2.5.1-acceptance-checklist.md.

HTTP and HTTPS access

The same-origin WebUI and session boundary are unchanged. Direct HTTP remains
appropriate only on a trusted network. Public or untrusted access must terminate
TLS at a trusted reverse proxy and enable HTTPS enforcement and secure cookies.

Direct managed-mount deployment

Managed NFS/SMB backup mounts remain opt-in. This patch does not change mount
capabilities, container paths, or host-side credential handling.

Compatibility and rollback

The database remains on Schema 8, and config.yaml remains limited to process bootstrap, listener, and security settings. Rollback to v2.5.0 requires stopping v2.5.1 and
restoring the matched pre-upgrade state backup before starting the previous
image because the one-way Xen Orchestra route-filter migration changes stored
route data.

Assets 2
Loading