Update version for the next release (v2.0.0-beta.1)

[meili-bot]

⚠️ This PR is automatically generated. Check the new version is the expected one.

Summary by CodeRabbit

• Chores
  • Updated library version to 2.0.0-beta.1.
  • Version identifiers shown in logs, diagnostics, and user-agent strings now reflect the new prerelease.
  • The reported qualified version string is now “Meilisearch PHP (v2.0.0-beta.1)”.
  • No changes to client behavior or APIs; existing functionality remains unaffected.

[coderabbitai]

Walkthrough

Updated Meilisearch::VERSION from '1.16.1' to '2.0.0-beta.1' in src/Meilisearch.php, changing qualifiedVersion() output to "Meilisearch PHP (v2.0.0-beta.1)". No other logic or flow modified.

Changes

Cohort / File(s)	Summary
Version bump src/Meilisearch.php	Updated public constant VERSION to '2.0.0-beta.1'; qualifiedVersion() now reports "Meilisearch PHP (v2.0.0-beta.1)".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update version for the next release (v1.15.0) #762 — Also updates Meilisearch::VERSION in src/Meilisearch.php.
• Update version for the next release (v1.16.1) #788 — Changes the same VERSION constant for reported library version.
• Update version for the next release (v1.16.0) #786 — Version bump in the identical constant and file.

Suggested reviewers

• Strift

Poem

A hop, a skip, a version leap—
From 1.x fields to beta steep.
My paws tap tags, my ears delight,
New string prints in the moonlit night.
Thump-thump—release is near, all right! 🐇✨

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 "Update version for the next release (v2.0.0-beta.1)" accurately and succinctly summarizes the primary change—bumping the VERSION constant to v2.0.0-beta.1 in src/Meilisearch.php—as indicated by the changeset and PR description; it is specific, concise, and appropriate for a release version update.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-version-v2.0.0-beta.1

---

📜 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 f9c00d3 and f85d282.

📒 Files selected for processing (1)

• src/Meilisearch.php (1 hunks)

🔇 Additional comments (1)

src/Meilisearch.php (1)

9-9: Approve SemVer prerelease bump to 2.0.0-beta.1

VERSION is '2.0.0-beta.1' in src/Meilisearch.php:9; qualifiedVersion() yields "Meilisearch PHP (v2.0.0-beta.1)"; SemVer validation passed. Ensure your release automation creates tag v2.0.0-beta.1 to match.

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