Update version for the next release (v0.34.0)

[ja7ad]

Summary by CodeRabbit

• Chores
  • Updated application version to 0.34.0. Users will see the new version in places where the version is displayed (e.g., About screen, app footer, CLI --version output, and logs). No functional changes or behavior differences are introduced with this update; it solely reflects the current release identifier for easier reference and verification across environments.

[coderabbitai]

Walkthrough

Bumped the exported VERSION constant in version.go from "0.33.3" to "0.34.0". No other code paths or functions were modified.

Changes

Cohort / File(s)	Summary
Version bump version.go	Updated const VERSION from "0.33.3" to "0.34.0".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update version for the next release (v0.33.1) #688 — Updates the same exported VERSION constant in version.go.
• Update version for the next release (v0.33.2) #701 — Bumps the VERSION constant in version.go for a subsequent release.
• Bump version from 0.33.2 to 0.33.3 #709 — Changes the VERSION constant in version.go to a newer release number.

Suggested labels

skip-changelog

Suggested reviewers

• ElyarSadig
• curquiza

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR updates the exported VERSION constant from "0.33.3" to "0.34.0" in version.go, and the title "Update version for the next release (v0.34.0)" succinctly and accurately summarizes that primary change for reviewers and history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my nose at 0.34.0’s gleam,
A hop from dots to dreams in the stream.
Version carrots lined in a tidy row—
Tag, nibble, merge, and off we go!
Thump-thump: release drums softly flow. 🥕✨

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.

---

📜 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 3b0d878 and 883e316.

📒 Files selected for processing (1)

• version.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: integration-tests (go latest version)
• GitHub Check: integration-tests (go current version)

🔇 Additional comments (1)

version.go (1)

5-5: LGTM: version bumped to v0.34.0

Change is correct; verification shows no references to 0.33.3 and VERSION defined once at version.go:5. Literal "Meilisearch Go (v0.34.0)" not found (likely generated at runtime). Tag the repo v0.34.0 and update CHANGELOG/README if applicable.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-to-0-34-0

---

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]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.98%. Comparing base (3b0d878) to head (883e316).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #718   +/-   ##
=======================================
  Coverage   85.98%   85.98%           
=======================================
  Files          22       22           
  Lines        3854     3854           
=======================================
  Hits         3314     3314           
  Misses        383      383           
  Partials      157      157           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.