Update version for the next release (v0.16.1)

[meili-bot]

This PR is auto-generated.

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

Summary by CodeRabbit

• Documentation

  • Updated installation snippets and code samples to reference meilisearch-java 0.16.1 (Maven and Gradle).
  • Ensures users installing from README and examples get the latest patch version.

• Chores

  • Bumped project version to 0.16.1 across the codebase.
  • Updated the reported SDK version string to reflect 0.16.1.
  • No functional changes; this is a maintenance release focused on aligning version references.

[coderabbitai]

Walkthrough

Updates project and documentation references from version 0.16.0 to 0.16.1 across build configuration, source version constant, and README/code samples. No API or behavioral changes are introduced.

Changes

Cohort / File(s)	Summary of Changes
Docs samples version bump README.md, .code-samples.meilisearch.yaml	Updated dependency snippets to use version 0.16.1 for Maven and Gradle.
Build configuration version bump build.gradle	Project version updated from 0.16.0 to 0.16.1.
Runtime version constant src/main/java/com/meilisearch/sdk/Version.java	static final String VERSION changed to "0.16.1" (affects reported qualified version string).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Update version for the next release (v0.14.7) #864 — Similar version bump across README, build.gradle, and Version.java.
• Update version for the next release (v0.14.6) #857 — Updates SDK version string in Version.java and associated references.
• Update version for the next release (v0.15.0) #870 — Consistent project/version constant and docs updates mirroring this change.

Suggested reviewers

• brunoocasali

Poem

A hop, a skip—now 0.16.1,
I nibbled numbers, work well done.
Build notes fresh, the README neat,
Version carrots taste so sweet.
Thump-thump! The release is spun. 🥕🐇

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.16.1)" is concise and directly summarizes the primary change in the PR (bumping the project/library version to 0.16.1), making it clear to reviewers what the intent of the changeset is.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 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 4557bac and 6498d77.

📒 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)

.code-samples.meilisearch.yaml (1)

466-466: Version refs updated in install snippets — LGTM.
Both Maven and Gradle snippets correctly point to 0.16.1.

Also applies to: 473-473

build.gradle (1)

20-20: Project version bumped to 0.16.1 — LGTM.
Matches the PR scope.

README.md (1)

61-61: Install instructions now reference 0.16.1 — LGTM.
Maven and Gradle snippets are consistent.

Also applies to: 71-71

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

4-4: VERSION constant updated to 0.16.1 — verified.
build.gradle and src/main/java/com/meilisearch/sdk/Version.java both set to 0.16.1; no stale 0.16.0 references found; README.md and .code-samples.meilisearch.yaml reference 0.16.1.

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

[meili-bors]

Build succeeded:

• linter
• integration-and-unit-tests