Find a way to make 'batch releases'
Open
Nobody has claimed this yet.
CI
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
When one of the base packages is updated (e.g. essreduce), we update the other packages at the same time in the PR.
But once it's merged and we release essreduce, we then have to manually bump minimum versions of essreduce in imaging and nmx, and then release these manually.
Sometimes, we would want to make automated batch releases where we release everything in one go. We should try to automate this.
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
No files, tests, or entry points are named. Start by tracing how the essreduce, imaging, and nmx packages are versioned and released, then define an automated batch-release flow that updates minimum versions and releases the packages together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100