Closed EvaSDK closed 1 year ago
The list of packages installed on the server: devpi-constrained-1.0.0 devpi-server-6.8.0 devpi-web-4.2.0
It looks like it is broken at the moment. The CI tests haven't run in a while (still on Travis), which is why I didn't notice. Locally I get test failures with latest devpi-server.
I have added GitHub Actions and released devpi-constrained 2.0.0.
Hello,
I wanted to test devpi-constrained for a while as our development team sometimes has difficulties keeping up with newer releases of our stack and it is not always easy to block a package to a certain version as it is used in a lot of repositories.
This is the case with tox and the latest release is causing trouble to our CI/CD pipeline as reported in https://github.com/tox-dev/tox/issues/2702.
Now, I rebuilt our Docker image with devpi-constrained and playing around with it, it does not seem to filter packages when it is used as the bases in another index.
Is this the intended behavior? Is my expectation that dev-team should get filtered results wrong?