Skip to content

Conversation

@meili-bot
Copy link
Contributor

@meili-bot meili-bot commented Dec 22, 2025

Description

This PR updates Meilisearch to version v1.31.0.

Changes

  • Updated appVersion in Chart.yaml
  • Bumped chart version (minor) in Chart.yaml
  • Updated image.tag in values.yaml
  • Updated compatibility section in README.md
  • Regenerated manifests/meilisearch.yaml

Release notes

See the Meilisearch v1.31.0 release notes.


🤖 This PR was automatically created by the update-meilisearch-version workflow.

Summary by CodeRabbit

  • Chores
    • Upgraded Meilisearch from v1.30.0 to v1.31.0 across all configuration files, Helm chart metadata, and Kubernetes deployment manifests.

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

@coderabbitai
Copy link

coderabbitai bot commented Dec 22, 2025

Walkthrough

Meilisearch version bumped from v1.30.0 to v1.31.0 across README documentation, Helm chart metadata and values, and Kubernetes manifests, with corresponding checksum updates in deployment configurations.

Changes

Cohort / File(s) Summary
README & Documentation
README.md
Updated compatibility note from v1.30.0 to v1.31.0
Helm Chart Configuration
charts/meilisearch/Chart.yaml, charts/meilisearch/values.yaml
Updated chart appVersion from v1.30.0 to v1.31.0, incremented chart version from 0.19.0 to 0.20.0, and updated container image tag
Kubernetes Manifests
manifests/meilisearch.yaml
Updated all resource version labels (ServiceAccount, ConfigMap, Service, StatefulSet) from v1.30.0 to v1.31.0, updated StatefulSet container image tag, and regenerated checksum annotation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

  • Straightforward version bump with identical pattern repeated across all files
  • Checksum update is automatically generated from configuration changes
  • No functional logic, control flow, or behavioral changes to evaluate

Possibly related PRs

Suggested reviewers

  • brunoocasali
  • curquiza

Poem

🐰 A hop and a skip, the versions align,
From thirty to thirty-one, everything's fine!
Charts and manifests dance in delight,
Checksums recalculate—all crisp and bright! ✨

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 pull request title clearly and accurately describes the main change: bumping Meilisearch from v1.30.0 to v1.31.0, which is reflected across all modified files (README, Chart.yaml, values.yaml, and manifests).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch bump/meilisearch-v1.31.0

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0382810 and 61f3d1e.

📒 Files selected for processing (4)
  • README.md
  • charts/meilisearch/Chart.yaml
  • charts/meilisearch/values.yaml
  • manifests/meilisearch.yaml
🔇 Additional comments (5)
charts/meilisearch/Chart.yaml (1)

2-2: LGTM! Version updates are consistent.

The appVersion and chart version have been updated correctly. The chart version follows semantic versioning with a minor bump (0.19.0 → 0.20.0), which is appropriate for a Meilisearch version update.

Also applies to: 5-5

manifests/meilisearch.yaml (3)

10-10: LGTM! Version labels updated consistently.

All Kubernetes resource labels have been updated to v1.31.0 consistently across ServiceAccount, ConfigMap, Service, and StatefulSet resources.

Also applies to: 23-23, 38-38, 60-60, 75-75


79-79: LGTM! Checksum updated as expected.

The config checksum annotation has been updated, which is expected when manifests are regenerated. This ensures pods will restart if the ConfigMap changes.


98-98: LGTM! Container image updated correctly.

The container image tag has been updated to v1.31.0, matching the appVersion in Chart.yaml.

charts/meilisearch/values.yaml (1)

22-22: LGTM! Image tag updated correctly.

The default image tag has been updated to v1.31.0, consistent with the appVersion in Chart.yaml and the container image in the generated manifests.

## 🤖 Compatibility with Meilisearch

This chart only guarantees the compatibility with the [version v1.30.0 of Meilisearch](https://github.com/meilisearch/meilisearch/releases/tag/v1.30.0).
This chart only guarantees the compatibility with the [version v1.31.0 of Meilisearch](https://github.com/meilisearch/meilisearch/releases/tag/v1.31.0).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Meilisearch v1.31.0 does not exist and must be corrected. The referenced version in the compatibility statement is non-existent. Verify the intended Meilisearch version (likely v1.30.0 or v1.30.1) and update the documentation accordingly. Recent versions include v1.30.1 (as of December 21, 2025).

🤖 Prompt for AI Agents
In README.md around line 99 the compatibility statement incorrectly references
Meilisearch v1.31.0 (a non-existent tag); verify the intended supported release
(likely v1.30.0 or v1.30.1), then update the version string and the release URL
to the correct Meilisearch tag (for example replace v1.31.0 with v1.30.1 and its
corresponding GitHub release link), and ensure any other README mentions match
that corrected version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants