UN-2453 [FIX] Fixed MistralAI failing test connection for some models#1440
UN-2453 [FIX] Fixed MistralAI failing test connection for some models#1440
Conversation
Summary by CodeRabbit
WalkthroughThe changes update the version constraint for the Changes
Sequence Diagram(s)No sequence diagram generated as the changes are limited to dependency version updates and do not affect control flow or feature logic. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
chandrasekharan-zipstack
left a comment
chandrasekharan-zipstack
left a comment
There was a problem hiding this comment.
LGTM - I think you might want to change the PR title prefix to FIX instead for it to appear in the changelogs correctly. Do check with @ritwik-g
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (3)
tools/classifier/requirements.txt (1)
7-7: Same concern as noted inprompt-service/pyproject.toml– please verify 0.76.1 resolves and locks are updated.tools/text_extractor/requirements.txt (1)
7-7: Same concern as noted inprompt-service/pyproject.toml– please verify 0.76.1 resolves and locks are updated.unstract/tool-registry/pyproject.toml (1)
14-15: Same concern as noted inprompt-service/pyproject.toml– please verify 0.76.1 resolves and locks are updated.
🧹 Nitpick comments (2)
backend/pyproject.toml (1)
38-42: Avoid version drift across >5 manifestsBumping the same library in many files is error-prone. Consider moving the version string to a central place (workspace-wide
tool.poetry.group, a Make/CI variable, or a shared constraints.txt) so that the next upgrade is single-touch.platform-service/pyproject.toml (1)
18-18: Remove stale inline comment
# Add versionis outdated and no longer meaningful now that the line has carried a version pin for several releases. Dropping it will avoid confusion.- "unstract-sdk[gcs, azure, aws]~=0.76.1", # Add version + "unstract-sdk[gcs, azure, aws]~=0.76.1",
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to Reviews > Disable Cache setting
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting
⛔ Files ignored due to path filters (5)
backend/uv.lockis excluded by!**/*.lockplatform-service/uv.lockis excluded by!**/*.lockprompt-service/uv.lockis excluded by!**/*.lockunstract/filesystem/uv.lockis excluded by!**/*.lockuv.lockis excluded by!**/*.lock
📒 Files selected for processing (8)
backend/pyproject.toml(1 hunks)platform-service/pyproject.toml(1 hunks)prompt-service/pyproject.toml(1 hunks)pyproject.toml(1 hunks)tools/classifier/requirements.txt(1 hunks)tools/text_extractor/requirements.txt(1 hunks)unstract/filesystem/pyproject.toml(1 hunks)unstract/tool-registry/pyproject.toml(1 hunks)
🔇 Additional comments (2)
unstract/filesystem/pyproject.toml (1)
9-9: unstract-sdk v0.76.1 Verified on PyPIConfirmed that
unstract-sdkversion 0.76.1 is published and available on PyPI. CI should now pass without issues—no further changes required.pyproject.toml (1)
40-40: Cross-check for stray 0.76.0 pinsThis file is updated, but other locations (Dockerfiles, requirements.txt, deployment manifests) may still reference
0.76.0. A quick grep before merging will prevent version drift between environments.
pk-zipstack
changed the title
|
|
…#1440) * bumped up unstract-sdk version to 0.76.1 * Commit uv.lock changes --------- Co-authored-by: pk-zipstack <187789273+pk-zipstack@users.noreply.github.com> Co-authored-by: Athul <89829560+athul-rs@users.noreply.github.com>
3 participants
What
0.76.1Why
mistral-mediumandmistral-largewere failing connections.How
0.76.1Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.