Update version for the next release (v0.17.1)

[meili-bot]

This PR is auto-generated.

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

Summary by CodeRabbit

• Chores
  • Updated library version to 0.17.1 across project dependencies, build configuration, and documentation.

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

[coderabbitai]

Walkthrough

This pull request bumps the meilisearch-java library version from 0.17.0 to 0.17.1 across build configuration, dependency declarations, code samples, and the internal version constant, with no functional changes.

Changes

Cohort / File(s)	Summary
Build and Configuration Files build.gradle, .code-samples.meilisearch.yaml, README.md	Version updated from 0.17.0 to 0.17.1 in Maven and Gradle dependency declarations and code-sample documentation
Version Constants src/main/java/com/meilisearch/sdk/Version.java	Internal VERSION constant value changed from "0.17.0" to "0.17.1"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• All changes are straightforward version number updates with no logic modifications
• Repetitive pattern across files reduces cognitive load

Possibly related PRs

• Update version for the next release (v0.14.6) #857: Updates project version string and corresponding build/readme snippets
• Update version for the next release (v0.15.0) #870: Updates Version.VERSION constant and matching docs/build version numbers
• Update version for the next release (v0.16.1) #895: Updates Version.VERSION constant and accompanying project/version references

Suggested reviewers

• Strift
• curquiza

Poem

🐰 A hop, a bump, a version rise,
From point-one-seven, version flies!
Zero point seventeen point one,
The rabbit's versioning work is done! ✨

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 'Update version for the next release (v0.17.1)' clearly and directly describes the main change across all modified files: bumping the project version from 0.17.0 to 0.17.1.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• 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 ae4b2f3 and 334ffae.

📒 Files selected for processing (4)

• .code-samples.meilisearch.yaml (1 hunks)
• README.md (2 hunks)
• build.gradle (1 hunks)
• src/main/java/com/meilisearch/sdk/Version.java (1 hunks)

🔇 Additional comments (4)

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.17.1", which will be reflected in the output of getQualifiedVersion().

README.md (1)

61-61: LGTM! Dependency documentation updated correctly.

The Maven and Gradle dependency version references have been properly updated to 0.17.1, ensuring users will reference the correct version when integrating the library.

Also applies to: 71-71

build.gradle (1)

20-20: LGTM! Project version bumped correctly.

The project version has been updated to 0.17.1, which will be used for artifact publication and distribution.

.code-samples.meilisearch.yaml (1)

466-466: LGTM! Code samples updated correctly.

The version references in the documentation code samples have been properly updated to 0.17.1, ensuring consistency across all getting-started examples.

Also applies to: 473-473

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[meili-bors]

Build succeeded:

• linter
• integration-and-unit-tests