Bump version string from 0.5.8 to 0.5.11

[reinaual]

Fixes #800

Summary by CodeRabbit

• Chores
  • Updated application version to 0.5.11 in release metadata.
  • No changes to features, interface, or behavior.
  • No updates to dependencies, scripts, or configuration affecting runtime.
  • Users should not expect any differences in functionality or performance.
  • This release serves as a version increment only, with stability and compatibility unchanged.

[coderabbitai]

Walkthrough

Incremented app/package.json version field from 0.5.8 to 0.5.11. No other changes.

Changes

Cohort / File(s)	Summary
Version bump app/package.json	Updated version from 0.5.8 to 0.5.11

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge the number, hop three steps more,
From 0.5.8 to .11 we soar.
No carrots moved, no scripts askew—
Just a tiny tag that says “we’re new.”
Thump-thump! Version tracks the lore. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Bump version string from 0.5.8 to 0.5.11" directly and precisely summarizes the primary change in the changeset (updating the version in app/package.json), is concise, and clearly communicates the intent to reviewers scanning the repository history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b0cad6b and b3e0231.

📒 Files selected for processing (1)

• app/package.json (1 hunks)

🔇 Additional comments (1)

app/package.json (1)

4-4: Version bump OK in app/package.json — search inconclusive; re-run repo-wide verification.

app/package.json shows 0.5.11; ripgrep returned "No files were searched" so absence of 0.5.8 elsewhere wasn't confirmed. Re-run:

fd -a package.json | while read -r f; do v=$(jq -r '.version // "<no version>"' "$f" 2>/dev/null || true); printf "%-60s %s\n" "$f" "$v"; done

rg -n -S --hidden --no-ignore --glob '!**/node_modules/**' '0\.5\.8' || true
rg -n -S --hidden --no-ignore --glob '!**/node_modules/**' '0\.5\.11' || true

Confirm no remaining references to 0.5.8 in package.json files, build scripts, docs/About dialogs, and that CI/release automation reads the bumped version (0.5.11).

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.11%. Comparing base (b0cad6b) to head (b3e0231).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #801   +/-   ##
=======================================
  Coverage   65.11%   65.11%           
=======================================
  Files          44       44           
  Lines        2935     2935           
=======================================
  Hits         1911     1911           
  Misses       1024     1024           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.