[BUG] Library incompatible with `protobuf >= 7.34.0`

[kxiong0]

Description

protobuf v34.0 removed deprecated field FieldDescriptor.label, which is referenced in internal/rules.py

This is causing AttributeError when calling protovalidate.validate(message)

Steps to Reproduce

1. Install protobuf >= 7.34.0
2. Run protovalidate.validate(message) on any message

Expected Behavior

protovalidate.validate(message) validates the protobuf message.

Actual Behavior

protovalidate.validate(message) raises an AttributeError

Screenshots/Logs

            if field.message_type.GetOptions().map_entry:
                key_field = field.message_type.fields_by_name["key"]
                value_field = field.message_type.fields_by_name["value"]
                if value_field.type != descriptor.FieldDescriptor.TYPE_MESSAGE:
                    continue
                result.append(MapValMsgRule(self, field, key_field, value_field))
>           elif field.label == descriptor.FieldDescriptor.LABEL_REPEATED:
E           AttributeError: 'google._upb._message.FieldDescriptor' object has no attribute 'label'

pip list | grep proto
protobuf                  7.34.1
protovalidate             1.1.0

Environment

• Operating System: Linux
• Version: Ubuntu 22.04
• Compiler/Toolchain: N/A
• Protobuf Compiler & Version: libprotoc 25.1
• Protovalidate Version: 1.1.0

Possible Solution

Migration: Rely on isRepeated and isRequired for cardinality and hasPresence to check for explicit presence tracking in singular fields.

https://protobuf.dev/news/2025-07-14/

Additional Context

[stefanvanburen]

hey @kxiong0, yeah I think that's vaguely related to #430. We probably ought to go ahead and do that migration.

[kxiong0]

hey @kxiong0, yeah I think that's vaguely related to #430. We probably ought to go ahead and do that migration.

Sounds great, tysm!

[stefanvanburen]

Actually:

protovalidate 1.1.0

@kxiong0 I think https://github.com/bufbuild/protovalidate-python/releases/tag/v1.1.2 should have fixed your issue; can you upgrade to that version (the latest) and see if you're still having trouble?

[kxiong0]

hey @stefanvanburen , upgrading fixed the error. I can't believe I missed this. Thanks!