Remove beta label from Advanced Search API#6396
Conversation
The Advanced Search API is no longer in beta. Slack thread: https://trychroma.slack.com/archives/C094URPR1E1/p1770705878908469?thread_ts=1770704741.803739&cid=C094URPR1E1 https://claude.ai/code/session_01Vx7tuNocjLqZzFfLsu5MWt
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
|
Please tag your PR title with one of: |
|
Documentation references in both Mintlify and Markdoc sources, along with the generated text exports, now remove the “(Beta)” qualifier from the Advanced Search API to reflect its GA status without requiring any functional code changes. Key Changes• Updated Affected Areas• Documentation: Cloud getting started pages and generated text exports This summary was automatically generated by @propel-code-bot |
3 participants
The Advanced Search API is no longer in beta.
Slack thread: https://trychroma.slack.com/archives/C094URPR1E1/p1770705878908469?thread_ts=1770704741.803739&cid=C094URPR1E1
https://claude.ai/code/session_01Vx7tuNocjLqZzFfLsu5MWt
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?