chore: bump version to 3.7.0

[Yeraze]

Summary

• Bumps version from 3.6.6 to 3.7.0 across package.json, Helm Chart, and Tauri config
• Adds news post for v3.7.0 highlighting the Auto Favorite feature

Changes Since v3.6.6

Features

• Auto Favorite automation for zero-cost hop routing (#2018)
• Position precision accuracy estimates on channel UI (#2008)
• Location indicators on all location-enabled channels (#2007)

Bug Fixes

• Packet routes use async DB methods for PostgreSQL/MySQL (#2016)
• Prevent duplicate outgoing messages in chat (#2015)
• Map position updates for mobile/tracker nodes and WebSocket position bug (#2014)
• Show optimized byte count when homoglyph setting is enabled (#2009)

Maintenance

• Clean up root markdown files (#2011)
• Bump production dependencies (#1992)
• Bump rollup dependencies (#1993, #1996)

System Test Results

Test Suite	Result
Configuration Import	PASSED
Quick Start Test	PASSED
Security Test	PASSED
V1 API Test	PASSED
Reverse Proxy Test	PASSED
Reverse Proxy + OIDC	PASSED
Virtual Node CLI Test	PASSED
Backup & Restore Test	PASSED
Database Migration Test	PASSED
DB Backing Consistency	PASSED

🤖 Generated with Claude Code

[github-actions]

Claude finished @Yeraze's task —— View job

---

PR Review: Version Bump to 3.7.0

Reviewing this version bump PR for code quality, best practices, potential bugs, performance considerations, security concerns, and test coverage.

Review Tasks:

• Examine package.json version changes
• Review package-lock.json consistency
• Check Tauri configuration version update
• Validate Helm Chart version changes
• Review news post content and format
• Check for missed version references
• Assess configuration changes for issues
• Provide comprehensive feedback

Review Findings

✅ Code Quality & Best Practices

• Version consistency: All version references correctly updated from 3.6.6 to 3.7.0
• File coverage: All necessary files updated (package.json, package-lock.json, tauri.conf.json, Chart.yaml)
• Semantic versioning: Minor version bump (3.6.6 → 3.7.0) is appropriate for the new Auto Favorite feature
• News post: Well-structured with comprehensive changelog and proper markdown formatting

✅ Version Update Validation

Files correctly updated:

• package.json:3 - Main version ✓
• package-lock.json:3,9 - Package lock version ✓
• desktop/src-tauri/tauri.conf.json:4 - Tauri app version ✓
• helm/meshmonitor/Chart.yaml:5,6 - Both chart version and appVersion ✓
• docs/public/news.json:6 - News post minVersion ✓

✅ Security Considerations

• No security concerns identified in version bump changes
• News post content is informational only, no executable code
• Configuration changes are standard version references

✅ Performance Considerations

• Version bump has no performance impact
• Package-lock.json shows some dependency optimization (removed duplicate entries)
• News post is well-structured JSON that won't impact load times

⚠️ Minor Documentation Inconsistency

Found outdated version references in documentation:

• docs/features/automation.md still references v3.4.0 in example tables
• docs/developers/auto-responder-scripting.md also references v3.4.0

These are in example documentation tables and don't affect functionality but could be updated for consistency.

✅ Test Coverage

• All system tests passing as reported in PR description
• Test coverage appears comprehensive based on the test suite results table
• No test updates needed for a version bump

✅ Package-lock.json Changes

The package-lock.json shows healthy changes:

• Version properly updated
• Some dependency metadata optimizations (devOptional → dev)
• No concerning dependency changes or security vulnerabilities introduced

Overall Assessment

This is a well-executed version bump PR that follows best practices:

1. Complete coverage: All relevant configuration files updated
2. Consistent versioning: No missed references in critical files
3. Proper documentation: Comprehensive changelog in news.json
4. Testing validated: Full system test suite passing
5. Clean changes: Only version-related modifications, no scope creep

Recommendations

1. Optional: Consider updating the version examples in documentation files (docs/features/automation.md and docs/developers/auto-responder-scripting.md) from v3.4.0 to v3.7.0 for consistency

2. Future improvement: Consider adding a script or CI check to validate all version references are updated consistently during version bumps

Approval Status

✅ Ready to merge - This PR meets all quality standards for a version bump and includes comprehensive testing validation.