Skip to content

release: v4.11.0-rc1#3531

Merged
Yeraze merged 1 commit into
mainfrom
release/4.11.0-rc1
Jun 17, 2026
Merged

release: v4.11.0-rc1#3531
Yeraze merged 1 commit into
mainfrom
release/4.11.0-rc1

Conversation

@Yeraze

@Yeraze Yeraze commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Release candidate v4.11.0-rc1

Bumps the version across all five tracked locations:

  • package.json + package-lock.json
  • helm/meshmonitor/Chart.yaml (version + appVersion)
  • desktop/package.json
  • desktop/src-tauri/tauri.conf.json

What's in 4.11.0 (since 4.10.4)

Note

tauri.conf.json carries the -rc1 semver pre-release tag — fine for the SemVer/npm/Helm toolchains; if the Windows MSI desktop build is strict about pre-release suffixes it'll surface in the release builds (this is an RC, so acceptable).

🤖 Generated with Claude Code

@Yeraze @claude
release: v4.11.0-rc1
caab4e5 
Release candidate for 4.11.0. Bumps the version across all five tracked
locations (package.json, package-lock.json, helm Chart.yaml version+appVersion,
desktop/package.json, desktop/src-tauri/tauri.conf.json).

4.11.0 carries the multi-source route-extraction refactors, the telemetry
ingestion unification (#3506/#3507/#3515), the auto-ping ack/race fix (#3522),
NodeInfo position-precision guard (#3516), backup-route hardening (#3524), and
the Node Details telemetry range selector (#3530).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Yeraze Yeraze added the system-test Trigger hardware system tests label Jun 17, 2026
@github-actions

github-actions Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown

Claude finished @Yeraze's task —— View job

PR Review: release/4.11.0-rc1

  • Gather context and read changed files
  • Review version consistency across all files
  • Check for potential issues
  • Post final review feedback

Summary

This is a clean, minimal version-bump PR. All five tracked locations are consistently updated to 4.11.0-rc1.

Version Consistency ✅

File Version
package.json 4.11.0-rc1
package-lock.json 4.11.0-rc1 (both root + packages[""] entries)
desktop/package.json 4.11.0-rc1
desktop/src-tauri/tauri.conf.json 4.11.0-rc1
helm/meshmonitor/Chart.yaml (version + appVersion) 4.11.0-rc1

No drift between files — all five locations are in sync.

Potential Concerns

Helm chart pre-release version — Helm's SemVer 2 support handles pre-release tags (-rc1) correctly for helm install/upgrade, but OCI registry pushes and some chart museum implementations may order pre-release versions below the previous stable release (e.g., 4.10.4 > 4.11.0-rc1 in SemVer ordering). This is expected SemVer behavior, not a bug, but worth knowing if the chart is published to a registry between now and GA.

Tauri / Windows MSI — As noted in the PR body, Tauri's bundler passes the version string directly to the WiX toolset. WiX MSI versions must be Major.Minor.Patch.Build (four numeric components, no pre-release strings). The -rc1 suffix will be stripped silently by Tauri's MSI bundler, so the installed version will show as 4.11.0.0 in Add/Remove Programs — acceptable for an RC but worth flagging so it's not surprising. The .AppImage and .deb targets handle pre-release strings fine.

No functional code changes — This PR only bumps version strings, so there are no logic, security, or performance concerns to raise.

Verdict

LGTM for an RC bump. The two notes above are informational rather than blocking.

@github-actions

github-actions Bot commented Jun 17, 2026

Copy link
Copy Markdown
System Test Results

MeshMonitor System Test Results

Test Run: 2026-06-17 17:39:40 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 2d7ae8d into main Jun 17, 2026
24 checks passed
@Yeraze Yeraze deleted the release/4.11.0-rc1 branch June 17, 2026 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

system-test Trigger hardware system tests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Yeraze