Skip to content

release: v4.10.3#3461

Merged
Yeraze merged 1 commit into
mainfrom
release/4.10.3
Jun 14, 2026
Merged

release: v4.10.3#3461
Yeraze merged 1 commit into
mainfrom
release/4.10.3

Conversation

@Yeraze

@Yeraze Yeraze commented Jun 14, 2026

Copy link
Copy Markdown
Owner

v4.10.3 — Traffic Management detection & bug fixes

Maintenance release. Version bumped to 4.10.3 across all five version files (package.json, package-lock.json, helm/meshmonitor/Chart.yaml, desktop/package.json, desktop/src-tauri/tauri.conf.json).

Highlights

Changes

  • CHANGELOG.md: promoted [Unreleased][4.10.3] - 2026-06-14 and added the five PRs merged after the section was last written.
  • docs/blog/2026-06-14-v4.10.3-traffic-management.md: new release blog post (Traffic Management + the bug-fix round).

Validation

  • tsc --noEmit: clean
  • Full Vitest suite: 6440 pass, 0 fail, 0 suite failures
  • System tests enabled via the system-test label on this PR.

🤖 Generated with Claude Code

Bump version to 4.10.3 across package.json, package-lock.json,
helm/meshmonitor/Chart.yaml, desktop/package.json, and
desktop/src-tauri/tauri.conf.json.

Finalize the CHANGELOG: promote [Unreleased] to [4.10.3] and add the
entries merged after the section was last written — MQTT NodeInfo
clobber fix (#3456), Traffic Management/StatusMessage firmware-version
gate (#3457), local-node module config storage (#3460), phantom channel
swap fix (#3453), and the TX power help-text clarification (#3459).

Add a release blog post highlighting the Traffic Management detection
fix and the bug-fix round.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 14, 2026

Copy link
Copy Markdown

Claude finished @Yeraze's task —— View job


✅ PR Review Complete

I've conducted a thorough review of this v4.10.3 release PR. Here's my comprehensive feedback:

🟢 Excellent - No Issues Found

Review Checklist:

  • Analyze changed files and version consistency
  • Review code quality and best practices
  • Check for potential bugs or issues
  • Evaluate security considerations
  • Assess test coverage implications
  • Review changelog and documentation updates
  • Provide comprehensive feedback

Code Quality & Best Practices ✅

Version Management:

  • Perfect version consistency across all 5 required files (package.json, package-lock.json, desktop/package.json, desktop/src-tauri/tauri.conf.json, helm/meshmonitor/Chart.yaml)
  • ✅ Follows repository's versioning policy exactly as specified in CLAUDE.md
  • ✅ Helm chart updates both version and appVersion correctly

Documentation:

  • Outstanding changelog quality - comprehensive, well-structured, follows Keep a Changelog format
  • Professional blog post - clear, informative, properly formatted with upgrade instructions
  • ✅ All changes properly categorized (Features, Bug Fixes) with appropriate detail level
  • ✅ Technical accuracy verified against recent commit history

Security Considerations ✅

Content Review:

  • ✅ No hardcoded credentials, secrets, or sensitive data
  • ✅ No console.log statements or debug code left behind
  • ✅ No TODO/FIXME/HACK markers in documentation
  • ✅ Blog post follows safe markdown practices
  • ✅ Version bumps are clean administrative changes only

Release Integrity:

Performance Considerations ✅

Minimal Impact:

  • ✅ Only version metadata and documentation changes - zero performance impact
  • ✅ No dependency updates that could affect runtime performance
  • ✅ Package-lock.json correctly regenerated maintaining dependency integrity

Test Coverage ✅

Release Validation:

  • ✅ PR description confirms full Vitest suite passed (6440 pass, 0 fail)
  • ✅ TypeScript compilation clean (tsc --noEmit)
  • ✅ System tests enabled via system-test label
  • ✅ No test changes needed for this maintenance release

Potential Issues ✅

CLAUDE.md Version Update:

  • ℹ️ Minor note: CLAUDE.md still shows "Version: 4.10.0" at line 3, but this is not a blocker as it's documentation metadata, not a functional version reference

Overall Assessment:
This is a textbook perfect maintenance release. All version files are correctly updated, documentation is comprehensive and professional, and the release properly packages the recent bug fixes. No issues found that would prevent merging.

✅ Recommendation: APPROVE

This release is ready to merge. Excellent work following all repository standards and best practices.


@Yeraze Yeraze added the system-test Trigger hardware system tests label Jun 14, 2026
@github-actions

Copy link
Copy Markdown
System Test Results

MeshMonitor System Test Results

Test Run: 2026-06-14 15:32:38 EDT

Test Summary

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
API Exercise (3 DBs) ✅ PASSED

✅ Overall Result: PASSED

All deployment configurations are working correctly!

Test Details

Configuration Import:

  • Tests configuration import and device reboot cycle
  • Verifies channel roles, PSKs, and LoRa configuration
  • Note: Channel name verification skipped due to architectural limitation

Quick Start Test:

  • Zero-config deployment (no SESSION_SECRET or COOKIE_SECURE required)
  • HTTP access without HSTS
  • Auto-generated admin user with default credentials
  • Session cookies work over HTTP
  • Meshtastic node connection and message exchange verified

Security Test:

  • Verifies Node IP address hidden from anonymous users in API responses
  • Verifies MQTT configuration hidden from anonymous users
  • Verifies Node IP address visible to authenticated users
  • Verifies MQTT configuration visible to authenticated users
  • Verifies protected endpoints require authentication

V1 API Test:

  • Tests v1 REST API endpoints with Bearer token authentication
  • Verifies Bearer token requests bypass CSRF protection
  • Verifies POST/PUT/DELETE work without CSRF token when using Bearer auth
  • Verifies session-based requests still require CSRF token

Reverse Proxy Test:

  • Production deployment with COOKIE_SECURE=true
  • HTTPS-ready configuration
  • Trust proxy enabled for reverse proxy compatibility
  • CORS configured for HTTPS domain
  • Meshtastic node connection and message exchange verified

Reverse Proxy + OIDC Test:

  • OIDC authentication integration
  • Mock OIDC provider health checks
  • Authorization flow and session creation
  • Hybrid mode (OIDC + local auth)
  • Meshtastic node connection verified

Virtual Node CLI Test:

  • Virtual Node Server enabled on TCP port 4404
  • Meshtastic Python client successfully connects
  • Node data download and synchronization verified
  • Test message sent on gauntlet channel (index 3)
  • Message delivery confirmed via Web UI API
  • Virtual Node Server connection logging verified

Backup & Restore Test:

  • System backup created from running dev container
  • New container spun up with RESTORE_FROM_BACKUP env var
  • Data integrity verified (node count, message count, settings)
  • Restore event logged in audit log
  • Dev container unaffected by restore test

Database Migration Test:

  • SQLite to PostgreSQL migration verified
  • SQLite to MySQL migration verified
  • Data integrity confirmed for both target databases
  • Row counts match between source and target

DB Backing Consistency Test:

  • SQLite, PostgreSQL, and MySQL backends tested with same device
  • Node counts within ±10 across all three backends
  • Favorite counts identical across all backends
  • Key station verified as favorite on all backends

@Yeraze Yeraze merged commit dbf0343 into main Jun 14, 2026
24 checks passed
@Yeraze Yeraze deleted the release/4.10.3 branch June 14, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

system-test Trigger hardware system tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant