Feature request: pin versions of python packages in CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
Today a lot of CI instances are blocked because flashinfer-python 0.2.6 is recently released and the CI installed the new version. The root cause is the requirements.txt references flashinfer-python~=0.2.3 which matches a lot of versions.
For example, blocked pipelines include
- PR #4792
- PR #4994
- PR #4998
I think we can PIN the versions of all python packages in CI to avoid breaks by 3rdparty.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with requirements.txt and the CI configuration for the affected pipelines. Identify how Python dependencies are currently resolved and determine the scope of pinning all CI packages. Done means CI installs fixed package versions and no longer breaks when newer third-party releases appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100