I would advice you to wait with this feature. I'm doing a complete refactor of the storage backend which will make this much easier. Currently it is very hard to get right with backward compatibility, replication and what have you.

Please keep this open though, it is a good use case to test my refactoring.

No problem thanks for giving it a look.

I needed this personally, otherwise my package manager tests skip all of the wheels :) but I can just install from my fork for now.

Let me know if you need anything.

Let me know if you want me to revisit this.

I was just contributing to pypi-timemachine, which is essentially doing the same thing as uv's exclude-newer, and noted this PR - having something like this would be super useful for that use case.

In devpi/devpi-constrained#12 I proposed seeing if there is an option, and interest, to re-use parts of simple-repository for handling some of the data model and logic. Since @fschulze suggests that there is a significant internal re-write, perhaps it is a good option to re-use such a library. I don't think simple-repository is perfect at this point, but it is a pretty good start, and I think integrating it into something like devpi would certainly lead to some improvement on the simple-repository side (which I would be most happy to do!).