fix: correct app version matched to release tag 4.11.2

[SarvasvaChaubey]

The release tagged 4.11.2 was built while the app version in package.json was still 4.11.1. This caused:

• Release asset filenames to show 4.11.1
• The app "About" dialog to report 4.11.1

This PR updates the root package.json version to 4.11.2 so future builds match the release tag and prevent version inconsistencies.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

The package version is incremented from 4.11.1 to 4.11.2 in the manifest file. This is a patch-level version bump with no functional code changes or control flow modifications.

Changes

Cohort / File(s)	Summary
Version Bump package.json	Version updated from 4.11.1 to 4.11.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰✨ A tiny hop, a number change,
From one-one to two so strange!
A patch release, so small yet bright,
The version dances through the night! 🌙

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: correcting the app version in package.json to match the release tag 4.11.2, which directly aligns with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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