docs: add changelog for v1.46 and v1.47#3597
Conversation
Add changelog entries for the v1.46 and v1.47 Meilisearch releases. v1.47: search personalization on federated search, the new settings indexer reaching feature completeness, additional Prometheus metrics, the unified search pipeline refactor, and user-facing search fixes. v1.46: the queueDocumentsFetch experimental feature, expanded settings indexer parameter support, and the v1.45.0 deletion-batching regression fix. The changelog had only reached v1.45, so v1.46 was added alongside v1.47 to keep the timeline contiguous.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughTwo new release changelog entries are prepended to ChangesChangelog Release Entries
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
changelog/changelog.mdx (1)
27-29: 💤 Low valueConsider clarifying the search pipeline refactor's error behavior change.
Line 29 states "some error messages have been updated and a few error codes have changed (for example,
MultiSearchErrorandSearchErrormay be swapped in certain cases)." The term "swapped" is slightly ambiguous—it could be clearer whether this means these codes are returned in different scenarios, or their meanings have changed. Users upgrading from v1.46 may need this detail to update error handling logic.Example clarification
Instead of "may be swapped in certain cases," you could write:
- "may be returned in place of the other in certain contexts"
- "in some scenarios, these codes may be returned differently than in v1.46"
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@changelog/changelog.mdx` around lines 27 - 29, The phrase "may be swapped in certain cases" when describing the behavior of `MultiSearchError` and `SearchError` is ambiguous and could confuse users upgrading from v1.46. Replace "swapped" with clearer language that explicitly describes that these error codes may now be returned in different scenarios or contexts than previously, such as "may be returned in place of the other in certain contexts" or "may be returned differently than in v1.46 in some scenarios" to help users understand they need to update their error handling logic accordingly.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@changelog/changelog.mdx`:
- Around line 27-29: The phrase "may be swapped in certain cases" when
describing the behavior of `MultiSearchError` and `SearchError` is ambiguous and
could confuse users upgrading from v1.46. Replace "swapped" with clearer
language that explicitly describes that these error codes may now be returned in
different scenarios or contexts than previously, such as "may be returned in
place of the other in certain contexts" or "may be returned differently than in
v1.46 in some scenarios" to help users understand they need to update their
error handling logic accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 011162bd-fb81-4a97-aaab-e78984c65bd8
📒 Files selected for processing (1)
changelog/changelog.mdx
|
@coderabbitai Addressed the nitpick: replaced the ambiguous "may be swapped in certain cases" wording with an explicit description ( |
|
Tip For best results, initiate chat on the files or code changes.
If you found this review helpful, would you consider giving us a shout-out on X? Thank you for using CodeRabbit! |
1 participant
What changed
Adds changelog entries for the v1.46 and v1.47 Meilisearch releases to
changelog/changelog.mdx.v1.47 (2026-06-15)
federationobject)rankingRulesordering,searchCutoffMs, and filters containing single quotes in remote/networked searchv1.46 (2026-06-08, merges v1.46.0 + v1.46.1)
queueDocumentsFetchexperimental featureWhy
Keeps the changelog up to date with the latest engine releases. The changelog had only reached v1.45, so v1.46 was added alongside v1.47 to keep the timeline contiguous (matching how the generator groups by minor version).
Notes for reviewers
generate-changelogscript requiresANTHROPIC_API_KEY, which was unavailable, so entries were authored manually from the GitHub release notes following the existing format and the script's filtering rules (excluding CI/dependency/internal-maintenance items).changelog/changelogpage, which renders all<Update>blocks as a timeline.Changelog additions for Meilisearch v1.47 and v1.46
Adds two consecutive release entries to
changelog/changelog.mdx:v1.47 (2026-06-15)
rankingRulesordering,searchCutoffMs, and filters with single quotes in remote/networked searchv1.46 (2026-06-08)
queueDocumentsFetchexperimental featureBoth releases are added at the top of the changelog to maintain a contiguous timeline from the previous v1.45 entries.