ci: fix requirements.txt

[leehanchung]

Description of changes

relax dependency with fastapi.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[propel-code-bot]

This PR updates the FastAPI dependency in requirements.txt, changing it from an exact version pin (==0.115.9) to a minimum version requirement (>=0.115.9). This allows the CI and codebase to accept newer FastAPI versions starting from 0.115.9, easing dependency management.

This summary was automatically generated by @propel-code-bot

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

[BestPractice]

The change from pinned version fastapi==0.115.9 to minimum version fastapi>=0.115.9 could introduce compatibility issues if future FastAPI versions have breaking changes. Consider whether this dependency should remain pinned to ensure consistent behavior across environments.

[leehanchung]

it is the exact reason why i am proposing relaxing the pinnned versions. chroma is a library code, and any pinned version has a very good chance to conflict with other library codes or application code that might be pinning fastapi versions.

not putting a bound to major version to stay consistent with the rest of the requirements.

[HammadB]

Thanks @leehanchung - agreed. I think it was intended to be pinned temporarily and never unpinned. We can remove this dep entirely now, since our server is in rust and we no longer use fastapi. cc @jairad26

[leehanchung]

Thank you. Look forward to the next release.