chore(dependencies): update pnpm-lock.yaml and Cargo.lock for package…

[M3gA-Mind]

… versions and add new dependencies

Summary

• What changed and why.
• Keep this to 3-6 bullets focused on user-visible or architecture-impacting changes.

Problem

• What issue or risk this PR addresses.
• Include context needed for reviewers to evaluate correctness quickly.

Solution

• How the implementation solves the problem.
• Note important design decisions and tradeoffs.

Submission Checklist

If a section does not apply to this change, mark the item as N/A with a one-line reason. Do not delete items.

• Tests added or updated (happy path + at least one failure / edge case) per docs/TESTING-STRATEGY.md
• Coverage matrix updated — added/removed/renamed feature rows in docs/TEST-COVERAGE-MATRIX.md reflect this change (or N/A: behaviour-only change)
• All affected feature IDs from the matrix are listed in the PR description under ## Related
• No new external network dependencies introduced (mock backend used per docs/TESTING-STRATEGY.md)
• Manual smoke checklist updated if this touches release-cut surfaces (docs/RELEASE-MANUAL-SMOKE.md)
• Linked issue closed via Closes #NNN in the ## Related section

Impact

• Runtime/platform impact (desktop/mobile/web/CLI), if any.
• Performance, security, migration, or compatibility implications.

Related

• Closes:
• Follow-up PR(s)/TODOs:

Summary by CodeRabbit

• Chores
  • Updated build configuration for error tracking settings.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c6cc0625-2a99-4732-abb9-99e475cef472

📥 Commits

Reviewing files that changed from the base of the PR and between 7bd83dd and 4318329.

⛔ Files ignored due to path filters (2)

• app/src-tauri/Cargo.lock is excluded by !**/*.lock
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• app/vite.config.ts

---

📝 Walkthrough

Walkthrough

The Sentry Vite plugin configuration in app/vite.config.ts was modified to add inject: false to the release object, preventing injection of the virtual release module into bundle startup code while retaining the computed release name.

Changes

Cohort / File(s)	Summary
Sentry Vite Configuration app/vite.config.ts	Added inject: false to the Sentry plugin's release configuration object to disable virtual release module injection into generated bundle code.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Suggested reviewers

• graycyrus

Poem

🐰 A config tweak so fine and small,
inject: false prevents the call,
The release stays, but bundled light,
Our startup code burns clean and bright! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title mentions updating dependency lockfiles, but the actual changeset only modifies Sentry Vite plugin configuration in app/vite.config.ts, not dependency lockfiles.	Update the PR title to accurately reflect the actual changes, such as 'chore(build): disable Sentry Vite plugin inject for release configuration' or similar.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Review rate limit: 4/5 reviews remaining, refill in 12 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}