Do we want concrete versions of dependencies, or not?

[matuskalas]

https://github.com/edamontology/caseologue/blob/main/caseologue_python/requirements.txt

At least some of the packages need to have a fixed version, to make sure the CI workflows don't suddenly start breaking.

• Fix the versions of all packages as the start. Merged in Added current versions to requirements.txt #12

• Set up a workflow or bot tool that would submit a PR if a dependency has a new version

• Consider later: Would it later be easier or harder to use with Conda / PyPI as a package, if the versions are fixed? Should maybe even some of the packages have fixed versions and some not? (And: Is Conda useful inside GitHub Actions at all? Perhaps useful as a standalone tool, but then decoupled from EDAM, ROBOT, ELK)

[matuskalas]

For info,
pip install -r requirements.txt --upgrade
installed the following today:
Successfully installed argparse-1.4.0 codespell-2.2.5 lxml-4.9.3 pandas-2.0.3 rdflib-7.0.0 tzdata-2023.3

@maanst