# PR review GitHub checks, org-wide API keys, and feature search from coding tools > 6 updates: PR reviews now create a GitHub check, Disable network log capture in mobile device presets, One API key for all your projects, PR review… Source: https://qa.tech/changelog/2026-06-11 --- 6 updates shipped on June 11, 2026. In this release 1. 01[PR reviews now create a GitHub check](#2026-06-11-pr-reviews-create-github-check)Highlight 2. 02[Disable network log capture in mobile device presets](#2026-06-11-disable-network-logs-mobile-presets) 3. 03[One API key for all your projects](#2026-06-11-one-api-key-for-all-projects) 4. 04[PR review override flow, live progress, and check-run fixes](#2026-06-11-pr-review-override-live-progress) 5. 05[Project IDs are now shown and copyable in the dashboard](#2026-06-11-project-ids-copyable-in-dashboard) 6. 06[Search your app's features from AI coding tools](#2026-06-11-search-features-from-coding-tools) 1. Highlight Featured this release ## PR reviews now create a GitHub check QA.tech's PR review now posts a "QA.tech / PR Review" check run so verdicts show up in the Checks tab and can be set as required before merging. A "request changes" finding marks the check failed; an approval marks it passed. To gate merging, add `QA.tech / PR Review` as a required status check in your branch protection rules – Settings → Integrations → GitHub shows the exact name with a copy button and setup steps. When a regression blocks a PR you need to merge anyway, an "Override" button on the failing check unblocks it without leaving GitHub. Reviews that don't complete auto-finalize as non-blocking after six hours. [\# Direct link](#2026-06-11-pr-reviews-create-github-check) 2. Update 02 of 06 ## Disable network log capture in mobile device presets A new "Capture Network Logs" toggle lets you turn off the network proxy for mobile tests where it interferes with app loading. Network log capture routes device traffic through a proxy to record HTTP calls, but it can block some apps from loading content. Open a mobile device preset and toggle "Capture Network Logs" off to run without the proxy. When capture is off, the Network Logs tab shows a clear notice. Existing presets are unaffected – capture stays on by default. [\# Direct link](#2026-06-11-disable-network-logs-mobile-presets) 3. Update 03 of 06 ## One API key for all your projects Org-scoped API keys can now target any project in your organisation – no more managing a separate key per project. Pass `projectShortId` on any API or MCP call to specify which project to act on. A new `list_projects` endpoint (`GET /v1/projects`) and MCP tool return all project short IDs under your key, completing a `create_project` → `list_projects` → operate loop without leaving the API. Project-scoped keys continue to work as before, locked to their own project. [\# Direct link](#2026-06-11-one-api-key-for-all-projects) 4. Update 04 of 06 ## PR review override flow, live progress, and check-run fixes Blocking PR reviews now surface a "Remove block →" link in GitHub and show live test progress while they run. The GitHub check-run and review comment now include a "Remove block →" link that opens the override dialog on the QA.tech dashboard. The dialog collects a reason before unblocking; following a stale link on a non-overridable check shows a "Nothing to override" explainer instead of silently doing nothing, and reviews stuck in-progress can be overridden to unblock a merge. While a review runs, the PR review card shows each test case in real time – status icons, screenshots, failure details, and links to results. Re-running the same commit now creates a fresh check run instead of stalling on the previous verdict. Under Settings → Integrations → GitHub, the auto-run toggle now explains when reviews fire and when to disable it to avoid double-reviews, and "Block merges when a review fails" is now a step-by-step branch protection guide. [\# Direct link](#2026-06-11-pr-review-override-live-progress) 5. Update 05 of 06 ## Project IDs are now shown and copyable in the dashboard The project overview now displays your project's prefixed ID so you can copy it directly into API calls and MCP tool configs. Open any project and look for the "Project ID" field in the overview panel – click it to copy the value to your clipboard. The ID is in `proj-slug_shortId` format (for example, `proj-my-app_aB12cD`). Pass it as `projectShortId` on any `/v1/` endpoint or MCP tool call. The `GET /v1/projects` list response now returns `shortId` in this same format, so scripts that enumerate projects get a ready-to-use value without transformation. [\# Direct link](#2026-06-11-project-ids-copyable-in-dashboard) 6. Update 06 of 06 ## Search your app's features from AI coding tools search\_features is a new MCP tool that finds features in your app by meaning, not just name. Pass one or more natural-language queries and get back the matching features, the pages they live on, and the UI actions QA.tech has observed – the same semantic search QA.tech's own chat uses. Combine with `list_features` and `get_feature` to browse or search the full picture of what your app does. Scope results to a specific project with `projectShortId`. [\# Direct link](#2026-06-11-search-features-from-coding-tools) ## Your team moves fast. Can your testing keep up? QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo. [Get a demo](https://qa.tech/demo) [QA.tech](https://qa.tech/) SOC 2 Type 2 compliant ![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png) ### Product - [Platform overview](https://qa.tech/product) - [AI QA Testing](https://qa.tech/ai-qa-testing) - [Web Testing](https://qa.tech/product/web-testing) - [Mobile Testing](https://qa.tech/product/mobile-testing) - [PR Testing](https://qa.tech/product/pr-testing) - [MCP](https://qa.tech/product/mcp) - [Use cases](https://qa.tech/use-cases) - [Changelog](https://qa.tech/changelog) ### Compare - [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress) - [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright) - [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl) - [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf) - [AI vs Human QA](https://qa.tech/saas) ### Resources - [Docs](https://docs.qa.tech/) - [Blog](https://qa.tech/blog) - [Events](https://qa.tech/events) - [Pricing](https://qa.tech/pricing) - [Case Studies](https://qa.tech/case-studies) ### Company - [About](https://qa.tech/about-us) - [Partnerships](https://qa.tech/partnerships) - [Press](https://qa.tech/press) - [Contact Us](https://qa.tech/contact) - [Privacy Policy](https://qa.tech/privacy-policy) - [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf) - [Security & Compliance](https://trust.qa.tech/) ### Social - [](https://www.linkedin.com/company/qa-tech-ai/) - [](https://x.com/getqatech) - [](https://www.instagram.com/getqatech/) © 2025 QA.tech. All rights reserved