Update version for the next release (v0.18.0)

[meili-bot]

This PR is auto-generated.

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

Summary by CodeRabbit

• Chores
  • Bumped project version to 0.18.0 across all build system configurations and version management files.
  • Updated documentation and code samples to reflect the new version 0.18.0 for consistency across all resources.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request bumps the project version from 0.17.1 to 0.18.0 across all relevant files: the build configuration, version constant, and documentation examples. No logic or control flow changes are introduced.

Changes

Cohort / File(s)	Summary
Version Bump .code-samples.meilisearch.yaml, README.md, build.gradle, src/main/java/com/meilisearch/sdk/Version.java	Unified version update from 0.17.1 to 0.18.0 across build configuration, static version constant, and all documentation/sample code references.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Update version for the next release (v0.15.0) #870: Performs identical version string updates across Version.java, build.gradle, README, and code-sample files for a release cycle.
• Update version for the next release (v0.14.6) #857: Follows the same version-bump pattern, updating version constants and corresponding build and documentation files.
• Update version for the next release (v0.17.0) #902: Applies the same code-level changes to version-related artifacts (Version.java, build.gradle, documentation samples) for a release bump.

Suggested reviewers

• curquiza
• brunoocasali

Poem

🐰 A version hops from point-one-seven to point-one-eight with glee,
Through gradle, maven, docs it bounds—consistent as can be!
No logic shifted, no flows bent, just numbers taking flight,
A tidy, clean release it is—everything feels right! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change—updating the version to v0.18.0 across all relevant files.

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb20799 and a872629.

📒 Files selected for processing (4)

• .code-samples.meilisearch.yaml
• README.md
• build.gradle
• src/main/java/com/meilisearch/sdk/Version.java

🔇 Additional comments (4)

.code-samples.meilisearch.yaml (1)

466-466: LGTM! Version strings updated correctly.

The Maven and Gradle dependency versions in the documentation samples have been updated consistently to 0.18.0.

Also applies to: 473-473

build.gradle (1)

19-19: LGTM! Artifact version updated correctly.

The published artifact version has been updated to 0.18.0, which will be reflected in Maven Central.

README.md (1)

60-60: LGTM! Installation instructions updated correctly.

Both Maven and Gradle dependency examples in the README have been updated consistently to version 0.18.0.

Also applies to: 70-70

src/main/java/com/meilisearch/sdk/Version.java (1)

4-4: LGTM! Version constant updated correctly.

The internal version constant has been updated to 0.18.0, ensuring the SDK properly reports its version at runtime through getQualifiedVersion().

---

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