qdrant/qdrant-client

Add release sanity check to CI

Closed

#958 opened on Apr 22, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (231 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (1,296 stars)
PR merge metrics
 (Avg merge 19d 5h) (6 merged PRs in 30d)

Description

We've already had 2 broken releases due to pytest leaking into the qdrant-client code (it was not in tests/). Both times it was figured out after making a release via just pip install qdrant-client in a fresh venv. This error makes us yank a broken package and release a patch version However, this problem could be easily detected during CI.

Contributor guide

Research direction
Inspect the existing CI workflow and add a step that installs the package in a fresh virtual environment (e.g., using venv) and verifies that only expected packages are installed, especially ensuring no pytest or test dependencies are included in the release.
Tech stack
python
Domain
ci cd
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80