chore: release v3.10.0

[Yeraze]

MeshMonitor v3.10.0

Major release featuring comprehensive database architecture refactoring — 5,672 lines of code removed across 278 files — plus new features and dozens of bug fixes.

New Features

• Channel drag-and-drop reorder with message history migration (feat: channel drag-and-drop reorder with message migration #2411)
• Dead nodes report with bulk delete on Security tab (feat: dead nodes report with bulk delete on Security tab #2414)
• Rsyslog server setting in network configuration (feat: add rsyslog server setting to network configuration #2410)
• Polar grid map overlay (feat: add polar grid leaflet overlay (#2307) #2359)
• Configurable default map center (feat: configurable default map center (#2317) #2350)
• Auto responder tokens as environment variables (feat: expose auto responder tokens as environment variables (#2314) #2356)
• Millisecond packet timestamps with date column (fix: packet log millisecond timestamps and date column #2403)
• OIDC retry on initialization failure (fix: OIDC init retries on failure instead of permanently disabling #2402)

Database Architecture

• Full async migration — all sync calls replaced (Phase 1-4: refactor: migrate sync database calls to async in small files (Phase 1) #2323, refactor: migrate server.ts sync calls to async repository (Phase 2) #2324, refactor: migrate meshtasticManager.ts sync calls to async repository (Phase 3) #2325, refactor: migrate remaining sync calls to async + Phase 4 cleanup #2328, refactor: remove 8 sync methods with async equivalents (Phase 4 final) #2330, refactor: migrate all remaining sync database callers to async #2332, refactor: remove dead sync code, fix remaining db access issues #2335)
• Repository pattern decomposition (refactor: wire migration registry + decompose DatabaseService facade (Phase 2+4) #2309, refactor: remove sync fallbacks + move SQL to repositories (Phase 4 continued) #2310)
• Centralized migration registry with v3.7 baseline (refactor: clean break migration system at v3.7 baseline (Phase 3) #2315)
• N+1 query elimination (refactor: fix N+1 queries, stale data, and write amplification in security scanner #2336, refactor: fix N+1 queries, timestamp units, and data integrity in neighbor info #2339, fix: use bulk query for getAllNodes to prevent PG pool exhaustion #2404)
• Cross-database helpers: col(), upsert(), insertIgnore(), getAffectedRows() (refactor: replace raw SQL duplication with col() helper for cross-DB quoting #2372, refactor: add getAffectedRows() helper to eliminate result extraction branching #2374, refactor: add upsert() and insertIgnore() helpers to eliminate conflict handling duplication #2376, refactor: replace hardcoded PG column quotes with col() helper #2389)

Bug Fixes

• Channel database no longer shadows device channels with same PSK (fix: channel database no longer shadows device channels with same PSK #2415, [BUG] https://github.com/Yeraze/meshmonitor/issues/2375 is still happening as tested in RC5 #2413, [BUG] Channel Database channel prevent traffic from reaching node channels on the UI #2375)
• PG pool exhaustion with 200+ nodes (fix: use bulk query for getAllNodes to prevent PG pool exhaustion #2404)
• Local node self-flagging security warnings (fix: prevent local node from self-flagging security warnings #2407)
• Key mismatch warnings not clearing (fix: PG packet monitor names and key mismatch flag not clearing #2406)
• Admin keys showing [object Object] (fix: admin keys showing as [object Object] in security config UI #2408)
• Traceroute race conditions and duplication (fix: resolve traceroute race condition for fast-responding nodes (#2364) #2366, fix: prevent duplicate traceroute pending records (#2364) #2380, fix: traceroute duplication caused by bypassing deduplication logic #2387)
• MQTT detection in traceroutes (fix: improve MQTT detection and visual distinction in traceroutes #2302)
• PKI_UNKNOWN_PUBKEY key mismatch flagging (fix: PKI_UNKNOWN_PUBKEY errors now correctly flag key mismatch #2382)
• PG packet monitor showing hex IDs (fix: PG packet monitor names and key mismatch flag not clearing #2406)
• Time offset flags not persisted on SQLite (fix: time offset flags not persisted on SQLite (#2378) #2379)
• Maintenance service scheduling drift (fix: prevent scheduling drift, timezone bugs, and data wipe in maintenance service #2338)

News

• Added v3.10.0 news.json entry for in-app notification

🤖 Generated with Claude Code

[github-actions]

Claude finished @Yeraze's task —— View job

---

PR Review for MeshMonitor v3.10.0 Release

Review Checklist:

• Examine version consistency across all files
• Review news.json entry for accuracy
• Check desktop configuration changes
• Verify Helm chart updates
• Assess security and best practices
• Provide final feedback

✅ Overall Assessment: APPROVED

This is a well-executed release PR that follows standard version bump practices. All changes are appropriate for a v3.10.0 release.

Code Quality & Best Practices ✅

• Version consistency: All 6 files correctly updated to 3.10.0
• Lockfile maintenance: package-lock.json properly updated with version changes
• Multi-platform support: Desktop (Tauri), web, and Helm chart all synchronized
• Release documentation: Comprehensive news entry with accurate feature descriptions

Security Considerations ✅

• No security concerns: This PR only contains version bumps and documentation
• No dependency changes: No new attack vectors introduced
• Standard release pattern: Follows established MeshMonitor release processes

Performance Considerations ✅

• Minimal impact: Version changes have no performance implications
• News entry optimization: Single JSON addition won't affect load times

Test Coverage Assessment

• Not applicable: Version bumps typically don't require new tests
• Existing CI: Should validate the build still works with updated versions

Technical Review

Desktop Configuration (desktop/src-tauri/tauri.conf.json:4)

• Version correctly updated to 3.10.0
• No other configuration changes (appropriate for version bump)

Helm Chart (helm/meshmonitor/Chart.yaml:5-6)

• Both version and appVersion updated consistently
• Maintains proper Helm chart versioning practices

News Entry Content Quality

• Excellent documentation: Comprehensive feature list with GitHub PR references
• Proper categorization: Release category with appropriate priority
• Accurate content: Matches the actual features delivered based on recent commits
• User-friendly: Well-formatted with actionable information

Recommendations

1. ✅ Ready to merge: No issues found
2. Consider: Running full test suite to verify version changes don't break anything
3. Post-merge: Verify the news notification displays correctly in the UI

---