chore: 📢 Bump version to 0.3.0

[openkaiden-bot]

📢 Bump version to 0.3.0

0.2.3 has been released.

Time to switch to the new 0.3.0 version 🥳

[coderabbitai]

Warning

Review limit reached

@benoitf, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 51 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d45b70af-9646-48f7-99d1-3e381172f037

📥 Commits

Reviewing files that changed from the base of the PR and between f5e0e2c and 94983ef.

📒 Files selected for processing (29)

• .flatpak-appdata.xml
• .github/ISSUE_TEMPLATE/bug_report.yml
• extensions/claude/package.json
• extensions/codex/package.json
• extensions/container/packages/api/package.json
• extensions/container/packages/extension/package.json
• extensions/copilot/package.json
• extensions/cursor/package.json
• extensions/docling/package.json
• extensions/gemini/package.json
• extensions/goose/package.json
• extensions/kdn/package.json
• extensions/mcp-registries/package.json
• extensions/milvus/package.json
• extensions/mistral/package.json
• extensions/ollama/package.json
• extensions/openai-compatible/package.json
• extensions/openclaw/package.json
• extensions/opencode/package.json
• extensions/openshell/package.json
• extensions/openshift-ai/package.json
• extensions/ramalama/package.json
• extensions/vertex-ai/package.json
• package.json
• packages/extension-api/package.json
• packages/preload-webview/package.json
• packages/renderer/package.json
• packages/webview-api/package.json
• tests/playwright/package.json

📝 Walkthrough

Walkthrough

Version bump PR that advances all package manifests from prior pre-release values to 0.3.0-next, adds a 0.2.3 release entry (dated 2026-05-13) to the Flatpak AppStream metadata file, and updates the GitHub bug report issue template to include 0.2.3 as a selectable version option.

Changes

Version bump to 0.3.0-next

Layer / File(s)	Summary
Release metadata: AppStream and bug report template .flatpak-appdata.xml, .github/ISSUE_TEMPLATE/bug_report.yml	Adds a <release> entry for version 0.2.3 dated 2026-05-13 to the AppStream metadata, and adds 0.2.3 as a selectable option in the bug report version dropdown.
Package version bumps to 0.3.0-next package.json, packages/*/package.json, tests/playwright/package.json, extensions/*/package.json	Bumps the version field to 0.3.0-next across the root manifest, all packages, the Playwright test suite, and all extension manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• openkaiden/kaiden#1789: Previous version-bump chore touching the same files — .flatpak-appdata.xml release entries and package.json/extension manifests.
• openkaiden/kaiden#1314: Directly related version-metadata bump updating .flatpak-appdata.xml, package.json version fields, and the bug report template dropdown.
• openkaiden/kaiden#1803: Same type of change to .github/ISSUE_TEMPLATE/bug_report.yml adding a version option to the dropdown.

Suggested reviewers

• benoitf
• gastoner
• fbricon

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the main change: bumping the project version to 0.3.0.
Description check	✅ Passed	The description matches the change and explains the 0.2.3 to 0.3.0 version switch.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.}

---

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