benya/rmm-openwrt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

release: prepare server 0.9.1

Browse Source
This commit is contained in:
benya
2026-07-31 01:47:10 +03:00
parent f492782aff
commit dd6bb747a5
25 changed files with 944 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/recent-progress.md
+10 -8
View File
@@ -18,24 +18,26 @@ Updated: 2026-07-31.
- Durable delivery queue with lease recovery, retries, dead-letter and retention.
- Built-in notification center with unread state, incident grouping and SSE refresh.
- Persistent LAN client presence with online, recent and unconfirmed states.
- Notification delivery metrics, channel diagnostics and filtered delivery history.
- Separate Profile, Security, Notifications and administrator-only Users tabs.
- LAN inventory filtering for failed/stale neighbour noise and IPv4 preference per MAC.
- Cloud-only wildcard router addressing; legacy DirectDNS routes are removed.
## Release state
- `server-v0.8.1` is published but predates the latest notification center and LAN client
changes.
- `server-v0.9.0` is published with the notification center, verified channels and LAN
client persistence.
- `agent-v0.6.8` is a signed tag; its complete current OpenWrt matrix and Pages deployment
finished successfully.
- `server-v0.9.0` is being prepared to include the current `main`, use a signed immutable tag and
be validated against a copy of the production SQLite database.
- `server-v0.9.1` is being prepared as a stabilization release for notification
operations, account navigation and LAN inventory cleanup.
## Next
The authoritative development order is maintained in `ROADMAP.md`. Immediate work is:
1. finish and verify the `agent-v0.6.8` package release;
2. publish and deploy a signed server release containing the current `main`;
1. publish the signed agent update manifest and verify package installation from the feed;
2. publish and deploy `server-v0.9.1` after a production database backup;
3. complete production notification, LAN-client and tunnel smoke tests;
4. add notification operational metrics;
5. move per-device tunnel credentials and signed/replay-protected commands ahead of
4. move per-device tunnel credentials and signed/replay-protected commands ahead of
backup/restore and remote update work.