Update version for the next release (v0.30.0)

[meili-bot]

This PR is auto-generated.

The automated script updates the version of meilisearch-rust to a new version: "v0.30.0"

Summary by CodeRabbit

• New Version

  • Package version bumped to 0.30.0.

• Chores

  • Internal dependency versions updated to align with 0.30.0.

• Documentation

  • README, templates, and code samples updated to reference meilisearch-sdk 0.30.0.

[coderabbitai]

Walkthrough

Version strings were updated from 0.29.1 to 0.30.0 across documentation snippets and Cargo manifests, including the main crate and the macro subcrate, plus the internal dependency reference. No logic or API changes.

Changes

Cohort / File(s)	Summary
Docs: meilisearch-sdk version bump README.md, README.tpl, .code-samples.meilisearch.yaml	Updated displayed meilisearch-sdk dependency from 0.29.1 to 0.30.0 in README and code-sample YAML.
Crates: package and internal dependency bump Cargo.toml, meilisearch-index-setting-macro/Cargo.toml	Bumped crate versions 0.29.1 → 0.30.0; updated meilisearch-index-setting-macro dependency to 0.30.0 (path preserved).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update version for the next release (v0.29.1) #687 — Mirrors dependency and crate version updates in the same files.
• Update version for the next release (v0.29.0) #684 — Similar version bumps across Cargo.toml, README, and code samples.

Suggested reviewers

• Mubelotix

Poem

A hop and a bump to three-oh-oh,
I twitch my nose—release notes glow. 🐇
Crates aligned, the numbers chime,
Docs refreshed in tidy rhyme.
Thump-thump! I sign with fluffy flair—
Version carrots everywhere! 🥕

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 (v0.30.0)" directly and concisely describes the PR's main change — bumping the crate and related documentation/examples to version 0.30.0 — and is clear enough for a reviewer scanning history to understand the primary intent.
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
• Commit unit tests in branch meili-bot/bump-version

---

📜 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 c5f63b6 and f2d5539.

📒 Files selected for processing (1)

• Cargo.toml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• Cargo.toml

⏰ 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). (1)

• GitHub Check: integration-tests

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

[curquiza]

bors merge

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Cargo.toml (1)

25-25: Internal macro dependency aligned to 0.30.0: OK.

Path + version are consistent; publish macro first, then the main crate to avoid resolution issues.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 606dfff and c5f63b6.

📒 Files selected for processing (5)

• .code-samples.meilisearch.yaml (1 hunks)
• Cargo.toml (2 hunks)
• README.md (1 hunks)
• README.tpl (1 hunks)
• meilisearch-index-setting-macro/Cargo.toml (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). (1)

• GitHub Check: integration-tests

🔇 Additional comments (6)

meilisearch-index-setting-macro/Cargo.toml (1)

3-3: Version bump looks good.

Matches the workspace update to 0.30.0.

README.md (1)

57-57: Update SDK version in docs: OK.

Snippet reflects 0.30.0.

Cargo.toml (2)

3-3: Crate version bumped to 0.30.0: OK.

No other metadata changes; fine for a release bump.

---

3-3: Resolved — no lingering "0.29.1"

rg returned zero matches for '0.29.1'; '0.30.0' appears in README.tpl, README.md, Cargo.toml, and meilisearch-index-setting-macro/Cargo.toml.

README.tpl (1)

57-57: Template version update: OK.

Ensures future README generations stay at 0.30.0.

.code-samples.meilisearch.yaml (1)

1063-1063: Docs sample dependency bumped: OK.

Rust getting-started sample now points to 0.30.0.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.63%. Comparing base (657a4d3) to head (f2d5539).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #708      +/-   ##
==========================================
- Coverage   85.69%   85.63%   -0.07%     
==========================================
  Files          19       19              
  Lines        5853     5853              
==========================================
- Hits         5016     5012       -4     
- Misses        837      841       +4     

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

[meili-bors]

This PR was included in a batch that successfully built, but then failed to merge into main. It will not be retried.

Additional information:

{"message":"Changes must be made through a pull request.","documentation_url":"https://docs.github.com/articles/about-protected-branches","status":"422"}