On 2026-03-11 09:27:57 -0500 (-0500), Tatiana Ovchinnikova wrote: [...]
- Tests are failing now since the older Horizon release is used, need to update it to 26.0.0 [...]
I think this shows a fundamental disconnect between release process and requirements handling. We should not be constraining type:service deliverables in cross-project testing, only type:library and type:client-library. If the horizon deliverable is actually being used more as a library then the deadline for making the final release was a month ago to give time for requirements updates. If it's really being used as a service then we should be testing with the current branch state and not relying on trying to get requirements updates merged during release candidate week when that was frozen weeks ago. I don't know how this should be solved for the current cycle, but it desperately needs to be revisited early next cycle. If it can't be reconciled, then affected jobs need to be setting horizon as a required-project and relying on tooling that installs it from Git instead of PyPI (and making on-the-fly edits to the constraints file to omit it at runtime). This currently works for normal Tox and DevStack based jobs, but I don't know which jobs you're referring to failing due to stale constraints so it's possible the jobs are simply misconfigured? -- Jeremy Stanley