7ea23da0c6
Problem: CI only tests the default feature set. The codebase defines multiple Cargo features (hardware, browser-native, sandbox-landlock, sandbox-bubblewrap, probe, rag-pdf) behind conditional compilation. Feature-gated code can silently break without CI coverage. Solution: Add a dedicated feature-matrix workflow that tests key feature combinations in a matrix strategy: - --no-default-features (bare minimum compiles) - --all-features (everything together) - --no-default-features --features hardware (isolated hardware) - --no-default-features --features browser-native (isolated browser) Each combination runs both cargo check and cargo test. The workflow triggers on Cargo.toml/lock/src changes and weekly schedule. Testing: Validated YAML syntax and matrix expansion logic. Actual feature compilation will be verified by CI on first run. Ref: zeroclaw-labs/zeroclaw#618 (item 2 — Feature Matrix Testing) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| codeql | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| actionlint.yaml | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| label-policy.json | ||
| labeler.yml | ||
| pull_request_template.md | ||