Plugin guard critical-finding scan and exclusion fixes
Cluster 109391. Data as of
Nothing open on GitHub. Fix merged in #110218 on 13 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #110218. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #110218. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how the plugin guard identifies and handles critical findings during install checks, including blocking behavior and the exclusion of test trees from scans.
Open issues0
Open PRs0
Fixes on record
-
#110218 plugin_guard: test trees no longer force a DANGEROUS verdict; block reason names the critical rule (#93927, #109391, salvage #89613 #109420)
files:
tests/tools/test_plugin_guard.py,tests/tools/test_plugin_guard_block_reason.py,tools/plugin_guard.py,website/docs/user-guide/features/plugins.md
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 1
- Closed#109391plugin_guard: one CRITICAL finding in a plugin's test suite blocks install outright (tests/docs not excluded, no per-finding waiver)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #110218
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 13 Sep 2026