chore: bump version to 3.10.0-RC6

[Yeraze]

Summary

Bump version to 3.10.0-RC6 across all 5 files.

Changes since RC5

• fix: database audit remediation across all 3 backends #2385 fix: database audit remediation across all 3 backends
• fix: database audit phase 2 — PG/MySQL crash prevention and schema alignment #2386 fix: database audit phase 2 — PG/MySQL crash prevention and schema alignment
• fix: traceroute duplication caused by bypassing deduplication logic #2387 fix: traceroute duplication caused by bypassing deduplication logic
• fix: packet monitor uses server time for consistent ordering #2388 fix: packet monitor uses server time for consistent ordering
• refactor: replace hardcoded PG column quotes with col() helper #2389 refactor: replace hardcoded PG column quotes with col() helper
• fix: add missing routePositions column to PG/MySQL traceroutes baseline #2390 fix: missing baseline columns + system backup column names + map preferences + API exercise test

🤖 Generated with Claude Code

[github-actions]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[github-actions]

Claude finished @Yeraze's task —— View job

---

PR Review: Version Bump to 3.10.0-RC6

Todo List

• Read and analyze all 5 changed files
• Verify version consistency across all files
• Check against CLAUDE.md requirements for version updates
• Review PR description and changelog
• Provide comprehensive feedback

---

✅ Code Quality & Best Practices

Excellent adherence to repository standards:

• All 5 required files have been updated correctly per CLAUDE.md requirements:
  • package.json:3 - Main version updated to 3.10.0-RC6
  • package-lock.json:3,9 - Both version fields updated consistently
  • desktop/package.json:4 - Desktop package version updated
  • desktop/src-tauri/tauri.conf.json:4 - Tauri config version updated
  • helm/meshmonitor/Chart.yaml:5,6 - Both version and appVersion updated

Version consistency: All files show the exact same version 3.10.0-RC6 - perfect consistency across the codebase.

✅ Security Considerations

No security concerns identified:

• This is purely a version metadata update
• No changes to code logic, dependencies, or security configurations
• All changes are in version declaration fields only

✅ Performance Considerations

No performance impact:

• Version bumps have zero runtime performance implications
• Only metadata changes that affect build/deployment artifacts

✅ Potential Issues & Suggestions

Minor considerations:

1. package-lock.json regeneration: According to CLAUDE.md, the lockfile should be regenerated via npm install --package-lock-only --legacy-peer-deps. The current changes appear manual but are correctly formatted.

2. CI/Testing: The previous GitHub Actions run encountered an error. Ensure the version bump doesn't introduce any unexpected build issues.

✅ Test Coverage

No test changes needed:

• Version bumps don't require test updates
• Existing test suite should validate the application still functions correctly
• System tests should be run before merging per repository guidelines

✅ Changelog Review

Well-structured PR description:

• Clear summary of changes since RC5
• Proper issue references (fix: database audit remediation across all 3 backends #2385-fix: add missing routePositions column to PG/MySQL traceroutes baseline #2390)
• Good categorization of fixes vs refactoring
• Appropriate RC versioning for pre-release

🎯 Overall Assessment

This is a clean, properly executed version bump that follows all repository conventions. The consistency across all 5 required files is perfect, and the changes appropriately reflect the new RC6 version.

Recommendation: ✅ Approve - This PR is ready to merge once CI passes successfully.

---