Switch uv resolution back to default (#427)

This switches our version resolution back to the default of "highest",
but leaves around our testing of our entire version range in CI. This
more closely follows [the recommendation of the uv team][1] for
libraries. This should help with resolving some of the GitHub security
alerts we get on this repository.

[1]: https://docs.astral.sh/uv/concepts/resolution/#resolution-strategy

Ref: connectrpc/connect-python#142
Ref: #373
Ref:
astral-sh/uv#18178 (comment)

Author: stefanvanburen

.github/workflows/ci.yaml

@@ -35,8 +35,8 @@ jobs:
       - run: make install
       - run: make lint
       - run: make format
-      # When running with matrix.resolution == highest, we expect uv.lock to change, but we don't want that file checked in.
-      - if: matrix.resolution == 'lowest-direct'
+      # When running with matrix.resolution == lowest-direct, we expect uv.lock to change, but we don't want that file checked in.
+      - if: matrix.resolution == 'highest'
         run: make checkgenerate
         env:
           BUF_TOKEN: ${{ secrets.BUF_TOKEN }}

pyproject.toml

@@ -22,6 +22,10 @@ classifiers = [
 ]
 dynamic = ["version"]
 dependencies = [
+  # We need at least this version, which fixed Python 3.14 compatibility (tp_new metaclass issue).
+  # The fix was never backported to the 5.x series.
+  # Ref: https://github.com/protocolbuffers/protobuf/pull/20594
+  "protobuf>=6.31.0; python_version >= '3.14'",
   "protobuf>=5",
   "cel-python>=0.5",
   # We need at least this version, which started publishing wheels for Python 3.14.
@@ -49,9 +53,6 @@ dev = [
   "types-protobuf>=5.29.1.20250315",
 ]
 
-[tool.uv]
-resolution = "lowest-direct"
-
 [tool.hatch.version]
 source = "vcs"
 raw-options = { fallback_version = "0.0.0" }