chore: bump version to 3.2.1

[Yeraze]

Summary

• Bumps version to 3.2.1 for hotfix release

Files Updated

• package.json
• package-lock.json
• helm/meshmonitor/Chart.yaml
• desktop/src-tauri/tauri.conf.json

🤖 Generated with Claude Code

[github-actions]

Claude finished @Yeraze's task —— View job

---

PR Review: Version Bump to 3.2.1

Todo List

• Read and analyze all 4 changed files
• Check version consistency across files
• Review for missing version references
• Check for security/quality concerns
• Provide comprehensive review feedback

---

Code Review Feedback

✅ Positive Aspects

Consistent Version Updates: All application version references have been updated consistently across the critical files:

• package.json:3 - Updated to 3.2.1
• package-lock.json:3,8 - Updated to 3.2.1 (both entries)
• helm/meshmonitor/Chart.yaml:5,6 - Both version and appVersion updated to 3.2.1
• desktop/src-tauri/tauri.conf.json:4 - Updated to 3.2.1

Proper Hotfix Process: This appears to follow proper semantic versioning for a patch/hotfix release (3.2.0 → 3.2.1).

Complete Coverage: The version bump covers all the necessary distribution channels:

• NPM package (package.json/package-lock.json)
• Helm chart deployment
• Desktop Tauri application

📋 Technical Analysis

Files Changed Analysis:

1. package.json - Main application version ✅
2. package-lock.json - Lockfile version consistency ✅
3. helm/meshmonitor/Chart.yaml - Both chart version and appVersion updated ✅
4. desktop/src-tauri/tauri.conf.json - Desktop app version ✅

Version Reference Validation:

• ✅ No stale version references found
• ✅ Timezone strings containing "3.2.0" are correctly left unchanged (these are DST format strings)
• ✅ Dependencies in package-lock.json with "3.2.0" versions are unrelated third-party packages

🔍 Code Quality Assessment

Best Practices: ✅ EXCELLENT

• Atomic commit with all version changes together
• No mixed concerns (version bump only)
• Clear, descriptive commit message and PR title

Security: ✅ NO CONCERNS

• No security-sensitive changes
• Standard version bump operations only

Performance: ✅ NO IMPACT

• Version string changes have negligible performance impact

Maintainability: ✅ GOOD

• Following the established pattern from CLAUDE.md instructions for version updates
• All required files updated per documented process

🎯 Final Assessment

This is a clean, well-executed version bump PR. The changes are:

• ✅ Consistent across all distribution channels
• ✅ Complete (no missing files)
• ✅ Follow semantic versioning conventions
• ✅ Properly scoped for a hotfix release

Recommendation: ✅ APPROVE - This PR is ready to merge.

Test Coverage: While no tests were modified, version bumps typically don't require additional test coverage as they're configuration changes rather than functional changes.

---