This repository was archived by the owner on Aug 11, 2026. It is now read-only.
Hide Chrome development flag warning and patch PHPCS - #219
Merged
ashfame merged 2 commits intoAug 11, 2026
Conversation
ashfame
changed the title
ashfame
merged commit Aug 11, 2026
78dc611
into
agent/maintenance-security-and-hygiene
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Chrome's
--test-typelaunch flag to both the development runner and production-preview runner.web-extinjects--disable-blink-features=AutomationControlledso its CDP-driven Chrome instance does not exposenavigator.webdriver = true. Chrome displays a generic unsupported-command-line-flag banner for that development-only browser;--test-typesuppresses the banner while retaining the behavior required byweb-ext.Refresh the locked PHP_CodeSniffer patch from 3.13.5 to 3.13.6. A high-severity command-injection advisory published after PR #199's previous validation caused its Composer audit gate to fail; 3.13.6 is the first patched release on the retained major.
Impact
The browser change affects only temporary Chrome instances launched by local npm development commands. It does not alter either packaged extension, Firefox behavior, or regular browser sessions. The Composer change is limited to the patched PHPCS development-tool lock entry.
Validation
npm ci --ignore-scripts.web-extaccepts both repeated--argvalues.npm run build:chrome; all three webpack targets compiled with only the existing Playground dynamic-dependency warning.squizlabs/php_codesnifferfrom 3.13.5 to 3.13.6.composer audit --locked; no security advisories remain.composer run lint; PHP CodeSniffer passed.git diff --check.