check runs added in v0.31 (#1999)

---------
Co-authored-by: Katie Horne <[email protected]>

Author: armchairlinguist

docs/semgrep-ci/network-broker.md

@@ -315,7 +315,7 @@ inbound:
       methods: [GET, POST]
 ```
 
-Semgrep also creates and updates [GitHub Checks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks#checks) when performing Managed Scans on pull requests. To ensure checks can be both created and updated, add the `PATCH` method to the preceding allowlist example, or add a separate entry to allowlist check updates:
+Semgrep also creates and updates [GitHub Checks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks#checks) when performing Managed Scans on pull requests. If you are running `v0.30.0` or earlier of the broker: to ensure checks can be both created and updated, add the `PATCH` method to the preceding allowlist example, or add a separate entry to allowlist check updates:
 
 ```yaml
 inbound:
@@ -325,6 +325,8 @@ inbound:
       methods: [GET, POST, PATCH]
 ```
 
+In broker `v0.31.0` and later, this URL is part of the default allowlist.
+
 ## Run multiple instances of the Semgrep Network Broker
 
 You can run multiple instances of the Semgrep Network Broker to manage availability. Semgrep handles multiple requests accordingly, preventing issues like duplicate PR or MR comments.