gRPC for PHP 1.82

Apply the PHP 8.5 baseline first. These rules cover the 1.82 line of the gRPC Core/PECL extension and its tagged PHP client wrappers. Use the officially documented PHP client APIs; native server classes do not establish a supported production PHP server stack.

Version, extension, and generated code

• Use these rules for auditing and migrating existing 1.82 clients; move production deployments to a supported, patched gRPC release line because 1.82 is outside the current-and-previous release support window.
• Verify the native extension with Grpc\VERSION or phpversion('grpc'), and pin the independently released grpc/grpc Composer library, protobuf runtime, authentication library, and build tools as a tested set. A Composer update alone does not patch the native C Core.
• Run these clients on supported PHP 8.5 builds. Do not treat the PHP >=7.1 library floor as a security support promise or impose the development-only grpc/grpc-dev protobuf constraint on the production library; check the actual packages and extension build selected for deployment.
• Generate clients only from reviewed .proto inputs using pinned protoc and grpc_php_plugin tools, review generated changes, and deploy a compatible protobuf runtime; do not pair newly generated code with an older runtime.

Targets, TLS, proxies, and discovery

• Create stubs from an allowlist of complete service targets, including resolver scheme, authority, and port; keep channel arguments, RPC method paths, deserializer classes, and grpc_call_invoker under application control.
• Set credentials