On 9/18/24 19:13, Stephen Finucane wrote:
o/
I'll jump straight into it. [...]
I very much agree with all you wrote. Though a few remarks...
Some project are still not under SQLAlchemy 2.x, like Zaqar, and I'm not sure for Trove (it switched to Alembic, and seems ok with SQLA 2.x: no unit test error that I could see).
From the release perspective, blocking OSC to 6.6.0 is ok for the moment, and it is my point of view that we should do it ASAP, so the release can move forward. We can repair the 7.x branch later, hopefully before the final releases.
What you describe is a general problem that started since we began using pinned versions for all libs. It could help to run a (non-voting) job that wouldn't have this constraint. In a more general way: making sure nothing is broken with the latest components is always a good thing.
Cheers,
Thomas Goirand (zigo)