chore: bump desktop version to 0.8.12

[benceruleanlu]

Summary

• bump desktop app version in package.json from 0.8.11 to 0.8.12

Merge after #1633

Summary by CodeRabbit

• Chores
  • Version bumped to 0.8.12.

┆Issue is synchronized with this Notion page by Unito

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the package version from 0.8.11 to 0.8.12 in package.json with a single-line modification. No functional changes, dependencies, or other files are affected.

Changes

Cohort / File(s)	Summary
Version Bump package.json	Updated package version from 0.8.11 to 0.8.12.

Possibly related PRs

• Bump desktop version to 0.8.1 #1584: Also performs a version bump in package.json with a single-line change.
• [chore] bump desktop version to 0.8.6 #1613: Updates the package.json version field in the same manner.
• chore: bump desktop version to 0.8.4 #1600: Modifies the package version in package.json without other code changes.

Suggested reviewers

• christian-byrne
• luke-mino-altherr

Poem

🐰 A tiny bump, from point one-one to one-two,
Just numbers dancing, nothing much to do,
The version hops along with gentle grace,
A small step forward in the software race! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: bump desktop version to 0.8.12' directly and accurately describes the single change in the pull request: a version bump in package.json.
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 (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-desktop-version-0.8.12

---

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.}

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report