cylc
protobuf: evaluate sensible version range
We pin the version of protobuf to ensure that the "protos" we compile are compatible with the runtime they are used in.
(note that as a distributed system, it's possible that different components of a Cylc system may be using different protobuf versions)
There is now an authoritative statement on cross version compatibility:
https://protobuf.dev/support/cross-version-runtime-guarantee/#major
https://protobuf.dev/support/cross-version-runtime-guarantee/#:~:text=minor%2C%20or%20micro).-,Python%2Dspecific%20Guarantees,-Since%20the%203.20.0
Given this, we may be able to loosen the version range.
Someone needs to carefully read through the content on this page and work out what a sensible range would be for us going forward.
If done quickly, this can supersede https://github.com/cylc/cylc-flow/issues/6885
@dwsutherland, would you be able to take a look?
If done quickly, this can supersede #6885
@dwsutherland, would you be able to take a look?
https://github.com/cylc/cylc-flow/pull/6972#issuecomment-3305049223
