Skip to content

Notifinho v2.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Jul 22:09
· 44 commits to main since this release
v2.5.0
a7f683d
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.0 release notes

Released 24 July 2026.

v2.5.0 makes SQLite authoritative for every WebUI-managed resource and reduces
config.yaml to process bootstrap, listener, and security settings.

Database-authoritative resources

  • Destinations and routes no longer depend on YAML synchronization.
  • API applications, regional preferences, backup scheduling, integration
    behavior, aliases, and Redfish deduplication settings are WebUI-managed.
  • Destination credentials remain in private secret files referenced by SQLite.
  • Dynamic destination type changes preserve the destination ID, route links,
    delivery history, and secret rotation boundary.

Fault isolation

  • A damaged destination or route row is reported independently while valid rows
    remain available.
  • A damaged integration-settings row falls back to its safe default and is shown
    as needing repair without breaking other settings.
  • Unexpected API failures include a safe error code, endpoint, and reference ID;
    the matching server log contains the traceback without credential values.

Migration

The first successful start upgrades platform state to Schema 8, imports v2.4
YAML resources, and atomically removes these sections from config.yaml:

  • outputs
  • routing
  • api.tokens
  • notifications
  • presentation
  • home_assistant
  • redfish
  • platform.backups
  • webui.language

Existing token values continue working because their hashes are imported. The
migration preserves file ownership and mode and creates a YAML backup.

Upgrade

  1. Back up the matched config, state, and secrets directories.
  2. Validate the migration in an isolated container using a copy of production.
  3. Deploy fortpt/notifinho:2.5.0 through the existing Portainer stack.
  4. Confirm schema 8, resource counts, token authentication, test deliveries,
    aliases, regional settings, and scheduled backups.
  5. Complete docs/v2.5.0-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. The migration moves backup schedule
and target selection into SQLite but does not change mount capabilities,
container paths, or host-side credential handling.

Compatibility and rollback

Rollback requires stopping v2.5.0 and restoring the matched pre-upgrade
config, state, and secrets backup before starting v2.4.0. v2.4.0 cannot
open schema 8 and normalized v2.5.0 YAML does not contain destinations or routes.

Assets 2
Loading