Docs.

Author: johnbillion

classes/Backtrace.php

@@ -427,7 +427,7 @@ public function filter_trace( array $frame ) {
 			/**
 			 * Filters which namespaces to ignore when constructing user-facing call stacks.
 			 *
-			 * @since 3.18.1
+			 * @since 3.19.0
 			 *
 			 * @param array<string, bool> $ignore_namespace Array of namespace names to ignore. The array keys are namespace names to ignore,
 			 *                                              the array values are whether to ignore the namespace (usually true).

collectors/http.php

@@ -390,7 +390,7 @@ public function process() {
 	/**
 	 * Log a Guzzle HTTP request.
 	 *
-	 * @since 3.18.1
+	 * @since 3.19.0
 	 *
 	 * @param \Psr\Http\Message\RequestInterface $request    The Guzzle request object.
 	 * @param \Psr\Http\Message\ResponseInterface|null $response The Guzzle response object, or null if an exception occurred.
@@ -474,7 +474,7 @@ public function log_guzzle_request( $request, $response, $exception, string $url
 	 *   $stack->push( QM_Collector_HTTP::guzzle_middleware() );
 	 *   $client = new Client( [ 'handler' => $stack ] );
 	 *
-	 * @since 3.18.1
+	 * @since 3.19.0
 	 *
 	 * @return callable Guzzle middleware callable.
 	 */

docs/wordpress-debugging/guzzle-http-requests.md

@@ -1,7 +1,7 @@
 # Debugging Guzzle HTTP Requests
 
 ::: tip New
-This feature is new in Query Monitor 3.18.1
+This feature is new in Query Monitor 3.19.0
 :::
 
 Query Monitor can log HTTP requests made with the [Guzzle HTTP client library](https://docs.guzzlephp.org/), a popular PHP HTTP client used by many WordPress plugins and applications. Since Guzzle bypasses WordPress's HTTP API, these requests don't normally appear in Query Monitor's HTTP panel. The Guzzle middleware solves this problem.