Skip to content

Nowlert v3.0.0

Latest
Latest

Choose a tag to compare

View all tags
@FortPT FortPT released this 03 Aug 09:32
· 28 commits to main since this release
v3.0.0
0adcfe3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Nowlert v3.0.0 release notes

Nowlert v3.0.0 finalizes the Nowlert product identity. The application, WebUI,
deployment examples, container metadata, repository, release title, and public
image coordinates use Nowlert and Theriark consistently.

Highlights

  • Product identity: Nowlert
  • Company identity: Theriark
  • Intended repository: Theriark/nowlert-ce
  • Docker Hub image: theriark/nowlert-ce
  • GitHub Container Registry image: ghcr.io/theriark/nowlert-ce
  • Development and production Compose identities use nowlert
  • WebUI update checks and public icon URLs target the Nowlert repository
  • Route migration preserves distinct generic, Redfish, and home-lab identities

Upgrade

  1. Back up config, state, secrets, logs, and external backup metadata as
    one matched set.
  2. Keep the existing v2.5.5 image available.
  3. Change the image to theriark/nowlert-ce:3.0.0.
  4. Use the documented internal /nowlert mounts.
  5. Start Nowlert and verify schema, login, destinations, routes, secrets,
    history, and real notification delivery.
  6. Keep the pre-upgrade backup until acceptance testing is complete.

Repository and registry cutover

The release workflow refuses stable publication unless it runs from
Theriark/nowlert-ce. Do not create the v3.0.0 tag while the repository remains
under FortPT/nowlert.

Before publication, verify:

  • repository transfer and rename are complete;
  • branch protections and Actions permissions are active;
  • Docker Hub credentials can push to theriark/nowlert-ce;
  • GitHub Actions can push to ghcr.io/theriark/nowlert-ce;
  • public repository and raw icon URLs resolve correctly.

Runtime contract and rollback

Nowlert 3.0.0 retains:

  • the NOWLERT_* environment namespace;
  • X-Nowlert-Token;
  • existing signature and idempotency headers;
  • existing event and platform schemas;
  • nowlert_session and nowlert_csrf;
  • nowlert.db;
  • nowlert-asset://;
  • /nowlert container paths;
  • existing backup formats;
  • database schema 9.

Rollback requires stopping Nowlert, restoring the complete matched pre-upgrade
configuration and state backup, and starting the previously pinned v2.5.5
image.

Database and configuration

No new database schema is introduced:

  • database schema: 9
  • configuration model: platform_database_v1

Acceptance

Complete
docs/v3.0.0-acceptance-checklist.md
before creating the stable tag or changing production.

Assets 4
Loading