QIT CLI 1.3.1 Release Notes
New Features
Added authenticated beta API fuzz testing
The new qit run:api-fuzz <extension> command runs schema-driven fuzz testing against plugin-owned WordPress REST API routes. It supports published extensions, uploaded development builds, synchronous and asynchronous execution, and normalized JSON results.
Lifecycle status is shown separately from the fuzz campaign state. The command waits up to 45 minutes by default, treats cancellation as terminal, and preserves the established QIT exit codes for success, warning, and failure.
See API Fuzz Testing for scope, campaign limits, result interpretation, and examples.
Improvements
- Managed-run JSON output decodes structured result fields instead of returning nested JSON strings.
- Asynchronous managed-run output includes the initial lifecycle status.
- All Manager-backed
run:*commands now accept a local ZIP, local directory, or remote HTTP(S) ZIP through--zip. - Managed
run:*commands now return failure exit code1when the Manager lifecycle status ishanged. qit getdisplays the API-fuzz campaign state and treats a cancelled run as finished.
Support and Feedback
If you have questions, encounter issues, or have suggestions, open a GitHub issue or run qit feedback "your message".
What's Changed
- Update snapshot by @zhongruige in #469
- Revert validation snapshot: "Tested up to" back to "5.8" for themes by @zhongruige in #470
- Require Docker Compose v2 instead of silently falling back to EOL v1 by @zhongruige in #472
- QIT-1006: Clarify repeatable environment reset contract by @zhongruige in #473
- QIT-1013: Reduce API-fuzz reset overhead by @zhongruige in #474
- Expose API fuzz testing through qit run:api-fuzz by @zhongruige in #475
Full Changelog: 1.3.0...1.3.1
Contributors
zhongruige