You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PHP extension client needs to build independently from the root Rust workspace while still testing against the in-tree Rust SDK. This adds the PHP binding package, Dockerized integration test path, and CI detection so PHP-only changes exercise the right checks.
Constraint: Foreign SDK crates are kept outside the root workspace like the existing Python and C++ SDKs
Constraint: PHP extension builds require php-config, cargo-php, and libclang in containerized CI
Rejected: Leave PHP tests manual only | PHP-only PRs would not run SDK-specific validation
Confidence: medium
Scope-risk: moderate
Directive: Keep foreign/php excluded from the root Cargo workspace unless the extension build is intentionally made workspace-compatible
Tested: cargo fmt --manifest-path foreign/php/Cargo.toml --check; composer validate --working-dir foreign/php --strict; PHP syntax lint for tests; cargo metadata --manifest-path foreign/php/Cargo.toml; docker compose config; docker compose build php-tests; PHP integration smoke against apache/iggy:latest with 23 passed, 3 skipped, 0 failed
Not-tested: Full docker compose test with source-built Iggy server after php-tests image build
0 commit comments