Imprecise version range of protovalidate-python dependency [request for upgrade]

[skoval00]

Recently I noticed that higher bound of version range for protovalidate-python dependency was increased to <1.2.0.

However authzed-py tests fail with protovalidate-python-1.1.1 because this release was significantly changed due to its upgraded dependency on cel-python-0.5: protovalidate-1.1.1 is tightly coupled with cel-python-0.5.

As far as I see, authzed-py locks protovalidate-1.0.0 in pyproject.toml. So to reproduce failing tests we need to upgrade protovalidate to the latest release 1.1.1 (I had to do this due to other dependencies in my system).

With upgraded protovalidate the tests for authzed fail for me like this

pytest flags: -m pytest
============================= test session starts ==============================
platform linux -- Python 3.13.9, pytest-8.4.2, pluggy-1.6.0
rootdir: /build/source
configfile: pyproject.toml
plugins: asyncio-1.2.0, time-machine-2.19.0
asyncio: mode=Mode.AUTO, debug=False, asyncio_default_fixture_loop_scope=None, asyncio_default_test_loop_scope=function
collected 0 items / 1 error

==================================== ERRORS ====================================
_____________________ ERROR collecting tests/misc_test.py ______________________
tests/misc_test.py:2: in <module>
    from protovalidate import ValidationError, validate
/nix/store/pkxl6xg85nqs7mfxqyjnfr0pjh6pa7na-python3.13-protovalidate-python-1.1.1/lib/python3.13/site-packages/protovalidate/__init__.py:15: in <module>
    from protovalidate import validator
/nix/store/pkxl6xg85nqs7mfxqyjnfr0pjh6pa7na-python3.13-protovalidate-python-1.1.1/lib/python3.13/site-packages/protovalidate/validator.py:18: in <module>
    from protovalidate.internal import extra_func
/nix/store/pkxl6xg85nqs7mfxqyjnfr0pjh6pa7na-python3.13-protovalidate-python-1.1.1/lib/python3.13/site-packages/protovalidate/internal/extra_func.py:23: in <module>
    from protovalidate.internal.rules import MessageType, field_to_cel
/nix/store/pkxl6xg85nqs7mfxqyjnfr0pjh6pa7na-python3.13-protovalidate-python-1.1.1/lib/python3.13/site-packages/protovalidate/internal/rules.py:513: in <module>
    class FieldRules(CelRules):
/nix/store/pkxl6xg85nqs7mfxqyjnfr0pjh6pa7na-python3.13-protovalidate-python-1.1.1/lib/python3.13/site-packages/protovalidate/internal/rules.py:538: in FieldRules
    validate_pb2.FieldRules.DESCRIPTOR.fields_by_number[validate_pb2.FieldRules.CEL_EXPRESSION_FIELD_NUMBER]
                                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E   AttributeError: CEL_EXPRESSION_FIELD_NUMBER
=========================== short test summary info ============================
ERROR tests/misc_test.py - AttributeError: CEL_EXPRESSION_FIELD_NUMBER
!!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!
=============================== 1 error in 0.37s ===============================

Could you please consider upgrading to protovalidate-1.1.1+ in one of your next releases?

[tstirrat15]

Sure, not a problem

[tstirrat15]

Just released https://github.com/authzed/authzed-py/releases/tag/v1.24.2. Can you let me know if it fixes the issue?

[skoval00]

Tanner, thanks for your response. Sorry. I think my message was a bit confusing, but 1.24.2 release also didn't help.

My problem is that I can only install protovalidate-1.1.1 and cel-python-0.5 in my environment (the latest versions), but in uv.lock of authzed protovalidate-1.0.0 and cel-python-0.2 are pinned.

I believe it's possible to reproduce the unit tests failure that I pasted in this issue, if protovalidate is upgraded

uv pip install protovalidate==1.1.1

When I installed those latest versions of authzed dependencies, I wanted to confirm that they are compatible. So I ran authzed tests and they failed with the error from my first message.

I have almost no experience with protobuf schema configuration, but I guess we need to regenerate https://github.com/authzed/authzed-py/tree/v1.24.2/src/buf/validate contents to make tests work. By running the following command in the root of authzed-py repo. Could you please check if this is correct and you generate them in the same way?

buf generate

[tstirrat15]

Ah, that makes sense. I'll get a PR up for that.

[tstirrat15]

That should be out in https://github.com/authzed/authzed-py/releases/tag/v1.24.3. Let me know if that works!

[skoval00]

Hi @tstirrat15 thank you for your help and fast response.

Now it works perfectly, tests run without errors with protovalidate-1.1.1.

Btw it seems to me, that protovalidate is not used by authzed in runtime and is only required for tests. I don't mind that at all. I just wonder what will happen if we move protovalidate from project.dependencies section to dependency-groups.dev?

[tstirrat15]

Hmm... I think I'd treat it as a peer dependency, if python dependencies have that idea. We generate code for protovalidate, but the use of protovalidate is optional to the user. Lemme see about that.