Automatically populate/update versions for popular pipelines

[michellewang]

We can probably set up some automation that checks the tags/releases of the GitHub repositories for pipelines that are currently in the catalog and updates the JSONs if needed.

Current repos that use GitHub releases:

• https://github.com/nipreps/fmriprep/
• https://github.com/nipreps/mriqc/
• https://github.com/PennLINC/qsiprep/
• https://github.com/scilus/tractoflow
• https://github.com/Donders-Institute/bidscoin (note that their release names != version names)
• https://github.com/UNFmontreal/Dcm2Bids/
• https://github.com/nipy/heudiconv

Repos that don't use releases but we could use some heuristic with git tags to get the versions:

• https://github.com/freesurfer/freesurfer

I don't think this is critical for now but it might be useful/needed for the addition of OpenNeuro derivatives in Neurobagel

@surchs @alyssadai

[surchs]

I think that's a good idea. We could say that when you publish a pipeline to the catalog, you should also provide the information for where a list of existing and future releases can be found. Definitely easier for people if a recognized pipeline is not refused just because we don't know the exact version yet.

One thing this does change though is that so far if a version was listed in the catalog, then that meant that Nipoppy has a tracker for it (or that's how I understood it). I still think that's a useful thing to know. So maybe we should also consider an attribute for this type of information: is there a known tracker for this version

[michellewang]

We have been thinking about using a Zenodo community to represent a curated subset of "high-quality" Nipoppy pipelines. We could add some CI (to this repo? or a new one?) to periodically download those records (using Nipoppy commands) and run some tests on them (i.e. the ones currently being run in the main repo which are being deleted since we are not storing pipeline configs there anymore). Then we can also (if desired) identify processing pipelines that have tracker config files and add them to the catalog here. Thoughts?