In skeleton we produced a requirements.txt from each CI build that could be dropped back in the repo to fix a failed build. No-one ever used this, and it was over complicated, but the issue of "my dependencies moved on and broke the tests" needs to be fixed.
I suggest the following strategy:
If dev-requirements.txt exists in the root of the repo then use it as a constraint in the devcontainer, runtime container, and CI when using the "dev" install (not for the matrix of tests)
Generate this in the "dev" install test and store as an artifact
Also upload this to the release
If tests fail, then tell people to grab the dev-requirements.txt from the latest release and it should fix things
In skeleton we produced a
requirements.txtfrom each CI build that could be dropped back in the repo to fix a failed build. No-one ever used this, and it was over complicated, but the issue of "my dependencies moved on and broke the tests" needs to be fixed.I suggest the following strategy:
dev-requirements.txtexists in the root of the repo then use it as a constraint in the devcontainer, runtime container, and CI when using the "dev" install (not for the matrix of tests)dev-requirements.txtfrom the latest release and it should fix things