Skip to content

Fix versions of Python dependencies for each distribution #610

@MakisH

Description

@MakisH

Triggered by #609, as well as by #584 and related issues, I think we need a mechanism to make the versions of our Python dependencies very specific every time we release a new distribution, for reproducibility reasons.

This could be included in a release pull request template here, and maybe there is some Action or similar mechanism to check the version restrictions in requirements.txt files.

However, if we do this by changing the actual files here, we would need to merge back-and-forth, which would be a bit ugly.

An alternative would be something like a Gemfile.lock approach, where we would specify a set of versions that are known to work in a separate file (for example requirements-reference.txt).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions