Auto-update software versions in modules
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of feature
As discussed on slack, it would be great to have some sort of automatic checking for new software releases, replacing the version lines in the module and opening a PR within the modules repository saving time and effort to keep up with new releases.
Phil mentioned, that some of the functionality is already there and could be extended:
I guess it should be possible to watch Bioconda for new releases and automatically create a PR with the new version / container IDs etc. I mean, the nf-core linting tool already checks for updates so we have most of the functionality there.
Just a case of getting the linting tool to actually apply the changes and then wrapping that up into a bot that runs nightly in a GitHub Actions workflow and creates a PR.
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 by locating the existing nf-core linting functionality that checks Bioconda releases and module updates. Define how it would apply version and container ID changes, then wrap it in a nightly GitHub Actions workflow that opens a pull request; completion means the automated update path works reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100