Update documentation for Meilisearch v1.50.0#3632
Conversation
- Update OpenAPI spec to v1.50.0 (new DELETE /dynamic-search-rules route) - Add cURL code sample for DELETE /dynamic-search-rules - Add DELETE /dynamic-search-rules to navigation (config/navigation.json) - Fix duplicate post_render_template_1 key in .code-samples.meilisearch.yaml - Add v1.50 changelog entry (breaking changes, new features, bug fixes)
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
The POST /render-template summary changed from 'Render documents with POST' to 'Render template' in v1.50, changing its Mintlify-generated URL from /reference/api/template/render-documents-with-post to /reference/api/template/render-template
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Description
Automated documentation update for Meilisearch v1.50.0 (released 2026-07-20).
Changes made
OpenAPI spec update
assets/open-api/meilisearch-openapi.jsonto v1.50.0assets/open-api/meilisearch-openapi-mintlify.jsonNew route: DELETE /dynamic-search-rules
DELETE /dynamic-search-rulesin.code-samples.meilisearch.yamlconfig/navigation.jsonChangelog
Bug fix: duplicate YAML key
post_render_template_1key that was incorrectly appended at the end of.code-samples.meilisearch.yamlby a previous automation runIssues encountered during automation
GitHub API rate limiting and download restrictions
The
fetch-meilisearch-openapi-filescript failed because:GH_TOKEN=proxy-injectedwas set in the environment, causing GitHub API to reject the token with 401The OpenAPI file was downloaded directly from the release asset redirect URL obtained via the proxy-compatible fetch mechanism.
SDK code samples returning 404
The
generate-mintlify-openapi-filescript warns that all SDK repos return 404 for their.code-samples.meilisearch.yamlfiles. This is expected: the SDKs have not yet added samples for many v1.50 features. No SDK samples were invented.Changelog generation skipped (no ANTHROPIC_API_KEY)
The
generate-changelogscript requiresANTHROPIC_API_KEY. The.envfile was not present in this environment and no API key was available. The changelog entry was written manually from the GitHub release notes.Still to check
DELETE /dynamic-search-rulesroute placement in navigation is correct (currently placed betweenPOST /dynamic-search-rulesandGET /dynamic-search-rules/{uid})GH_TOKEN=proxy-injectedissue for future automation runs (the env var causes 401 when passed to GitHub API)Checklist
Generated by Claude Code