qdrant server v1.16.3 not updated to v1.18 — client/server version mismatch in dev environment

[bug-ops]

Description

After upgrading `qdrant-client` crate to 1.18.0 (#3766) and updating the docker-compose image tag to `qdrant/qdrant:v1.18.0` (#3759), the locally running Qdrant container was not restarted. The container still runs `v1.16.3`.

On every Zeph startup, the following warning is printed to stdout:

Client version 1.18.0 is not compatible with server version 1.16.3.
Major versions should match and minor version difference must not exceed 1.
Set check_compatibility=false to skip version check.

The client accepts this and continues (due to the non-fatal nature of the check), but API compatibility is not guaranteed.

Reproduction Steps

1. Run docker inspect zeph-qdrant-1 --format "{{.Config.Image}}" — returns qdrant/qdrant:v1.16.3
2. Run cargo run --features full -- --config .local/config/testing.toml --bare with any prompt
3. Observe the compatibility warning on stdout

Expected Behavior

The dev Qdrant container should be running v1.18.0 matching the client version. No compatibility warning.

Actual Behavior

Container still on v1.16.3. Client 1.18.0 warns about 2-minor-version gap exceeding the allowed tolerance.

Environment

• qdrant-client crate: 1.18.0 (Cargo.lock)
• Qdrant server: v1.16.3 (running container zeph-qdrant-1)
• docker-compose image: updated to v1.18.0 in chore(deps): update qdrant/qdrant docker tag to v1.18.0 #3759 but container not restarted
• Platform: macOS Darwin 25.4.0

Fix

docker compose -f docker/docker-compose.deps.yml pull qdrant
docker compose -f docker/docker-compose.deps.yml up -d qdrant

[bug-ops]

Fixed by pulling the updated image and recreating the container:

docker compose -f docker/docker-compose.deps.yml pull qdrant
docker compose -f docker/docker-compose.deps.yml down
docker compose -f docker/docker-compose.deps.yml up -d qdrant

Verified: curl http://localhost:6333/ now returns "version":"1.18.0". The client/server version mismatch warning is resolved.

[bug-ops]

Qdrant container updated to v1.18.0 (image: qdrant/qdrant:v1.18.0@sha256:1cf3e07...) as of CI-750. WARN on startup should be resolved. Verified: docker inspect shows v1.18.0.