[FIX] Bump bundled Qdrant server to v1.16.1 to match qdrant-client

[amanattrish]

What

Bump the bundled Qdrant server image from v1.8.3 to v1.16.1 in docker/docker-compose-dev-essentials.yaml.

Why

unstract/sdk1 pins qdrant-client>=1.16.0,<1.17.0 (#1845) but the compose file still ran the 1.8.3 server (set in #185). The version gap makes the client hit an API path the old server does not expose, so adding the bundled Qdrant as a vector DB fails on test connection with 404 (Not Found).

How

Changed the image tag to v1.16.1, which is within the client's supported range.

Can 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)

Fresh installs: no risk, the vector store starts empty.
Existing installs: the persisted qdrant_data volume was created by 1.8.3. Qdrant keeps storage backward compatible, so 1.16.1 should read it, but I have only tested a fresh setup. Flagging so maintainers can confirm the upgrade path.

Database Migrations

None.

Env Config

None.

Relevant Docs

None.

Related Issues or PRs

Fixes #2014.

Dependencies Versions

Qdrant server image: v1.8.3 -> v1.16.1 (aligns with qdrant-client 1.16.2).

Notes on Testing

• Bumped the tag and recreated the container: docker compose -f docker-compose.yaml up -d --force-recreate qdrant
• curl http://localhost:6333/ reports version 1.16.1.
• Onboarding > Connect Vector Database > Qdrant with http://unstract-vector-db:6333 now passes test connection.
• Backend logs no longer show the client/server incompatibility warning.

Screenshots

Checklist

I have read and understood the Contribution Guidelines.

[CLAassistant]

All committers have signed the CLA.

[greptile-apps]

Greptile Summary

Bumps the bundled Qdrant server Docker image from v1.8.3 to v1.16.1 in the dev-essentials Compose file, aligning it with the qdrant-client>=1.16.0,<1.17.0 pin introduced in the SDK. This resolves a 404 error when the newer client called an API path not available on the old server.

• Single-line change in docker/docker-compose-dev-essentials.yaml; no other Compose files reference Qdrant, so there is no drift elsewhere.
• Existing qdrant_data volumes created by 1.8.3 should be forward-compatible, but only fresh installs have been explicitly tested by the author.

Confidence Score: 5/5

Safe to merge; the change is a targeted version bump that fixes a documented client/server mismatch.

The only change is a single image tag in the dev Compose file. It brings the server version into the range already required by the pinned client library, directly fixing the reported 404. No application code, migrations, or configuration is affected. Qdrant's storage format is backward-compatible, so existing volumes are not at risk.

No files require special attention.

Important Files Changed

Filename	Overview
docker/docker-compose-dev-essentials.yaml	Single-line bump of the Qdrant server image tag from v1.8.3 to v1.16.1 to match the qdrant-client>=1.16.0,<1.17.0 constraint in the SDK.

Sequence Diagram

sequenceDiagram
    participant SDK as unstract/sdk1 (qdrant-client 1.16.x)
    participant Server as Qdrant Server

    Note over SDK,Server: Before (v1.8.3 server)
    SDK->>Server: API call (1.16.x endpoint)
    Server-->>SDK: 404 Not Found

    Note over SDK,Server: After (v1.16.1 server)
    SDK->>Server: API call (1.16.x endpoint)
    Server-->>SDK: 200 OK

Loading

_{Reviews (1): Last reviewed commit: "[FIX] Bump bundled Qdrant server to v1.1..." | Re-trigger Greptile}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a30dab92-c9bf-447b-86e3-0f9c835d70d1

📥 Commits

Reviewing files that changed from the base of the PR and between f722a69 and b2bfcbd.

📒 Files selected for processing (1)

• docker/docker-compose-dev-essentials.yaml

---

Summary by CodeRabbit

• Chores
  • Updated development environment dependencies to the latest stable versions.

Walkthrough

The pull request updates the Qdrant vector database service image from v1.8.3 to v1.16.1 in the development Docker Compose configuration. This single-line change addresses a compatibility issue between the bundled Qdrant server and qdrant-client 1.16, which caused test connection failures during onboarding.

Changes

Qdrant Version Update

Layer / File(s)	Summary
Update Qdrant service image docker/docker-compose-dev-essentials.yaml	Qdrant service Docker image bumped from qdrant/qdrant:v1.8.3 to qdrant/qdrant:v1.16.1 to align with qdrant-client 1.16 compatibility requirements. No other service configuration or wiring changed.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately summarizes the main change: bumping the bundled Qdrant server version to align with the qdrant-client dependency.
Description check	✅ Passed	The description comprehensively covers all template sections: What/Why/How, impact analysis, dependencies, testing notes, and related issues. All required sections are filled with clear, relevant information.
Linked Issues check	✅ Passed	The PR directly fixes issue #2014 by updating the Qdrant server image from v1.8.3 to v1.16.1, resolving the API incompatibility that caused 404 errors during vector DB test connection.
Out of Scope Changes check	✅ Passed	The change is narrowly focused on updating the Qdrant image tag in the Docker Compose file, with no extraneous modifications. This is directly scoped to address the version mismatch issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}