Repository navigation
chore: allow new versions that fix high or critical advisories in check-dependency-age - #44110
Conversation
…ck-dependency-age
This comment has been minimized.
This comment has been minimized.
c359de0
into
microsoft:main
🟢 The reported failure is a pre-existing flakeI'm the Playwright bot. I checked the failure against the PR changes and test history. DetailsCovers tests 1, run 43520341306, for PR revision Pre-existing flake / infra
The popup test passed on retry, so it is not a failure group. The triggering run was cancelled; this verdict covers the reported results, not the missing results or the newer PR revision. Checked the failures on Linux by the Playwright bot - agent run |
Test results for "tests 1"23638 passed, 716 skipped Merge workflow run. |
Test results for "MCP"3 failed 5232 passed, 631 skipped Merge workflow run. |
Summary
package-lock.jsonthat is less than 7 days old now passes when it fixes an advisory of high or critical severity, and no version that is at least 7 days old fixes it.Example for the lock file from #44100, which still fails: