scikit-learn / scikit-learn/scikit-learn-release
Remove chain input from wheels.yml?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 4
- Avg merge
- 7h 51m
- Merged PRs (30d)
- 5
Description
I'd rather mirror closely what numpy and scipy are doing, while we are getting more familiar with the release process.
I guess it was done to be more convenient, you build and test all the wheels, approve upload on testpypi.org, test locally, and then can approve the upload to PyPI. Without the chain workflow you have to build and test twice, which is quite costly since right now can take 1-2 hours (because of the macOS 5 concurent runners limitation + the fact that we have 7 slow macOS-intel build and 7 faster macOS arm builds).
Contributor guide
No contributing guide indexed for this repository
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
Read wheels.yml first and trace how the chain input controls the wheel build, TestPyPI upload, and PyPI upload steps. Compare the workflow shape with the numpy and scipy release workflows, then confirm that the chain input is removed and the resulting release process still matches the intended manual sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, release
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100