I've noticed that I (manually, as one currently has to) updated digraphs-lib from version 0.6 to version 0.7. This process happens independently of the Digraphs repository and pull requests here, so I didn't notice that it broke the Digraphs CI, which explicitly was looking for digraphs-lib-0.6.tar.gz, which no longer exists.
It would be good if the Digraphs CI could instead use a URL for digraphs-lib that always defaulted to the latest version.
Resolving #823 by having digraphs-lib be its own repository as suggested in #823 (comment) could solve this failing-CI version in two ways: firstly, releasing digraphs-lib-0.7.tar.gz wouldn't do anything to affect the continued existence of digraphs-lib-0.6.tar.gz, but also you could make use of the GitHub "latest" concept (e.g. the existence of URLs such as https://github.com/digraphs/Digraphs/releases/latest) to mean that the CI could automatically always use the latest version of the library.
cf. #823.
I've noticed that I (manually, as one currently has to) updated
digraphs-libfrom version 0.6 to version 0.7. This process happens independently of the Digraphs repository and pull requests here, so I didn't notice that it broke the Digraphs CI, which explicitly was looking fordigraphs-lib-0.6.tar.gz, which no longer exists.It would be good if the Digraphs CI could instead use a URL for
digraphs-libthat always defaulted to the latest version.Resolving #823 by having
digraphs-libbe its own repository as suggested in #823 (comment) could solve this failing-CI version in two ways: firstly, releasingdigraphs-lib-0.7.tar.gzwouldn't do anything to affect the continued existence ofdigraphs-lib-0.6.tar.gz, but also you could make use of the GitHub "latest" concept (e.g. the existence of URLs such as https://github.com/digraphs/Digraphs/releases/latest) to mean that the CI could automatically always use the latest version of the library.cf. #823.