← proof

Fixed in 3 of 3 runs: tests passed before and after, flaky excluded, 0 regressions

nearform/ag-grid-url-sync #152 · @vitest/coverage-v8 4.1.11 → 5.0.0 · head d4498381b2b5 · failing on the PR: Lint and test · npm@11 · node 22 (unpinned; default) · run 2026-09-17

This repository names Node 22 (unpinned; default); the run used Node 26.7.0, with npm's engine check off for the base install.

Trial 1: green

Tests

Files changed

• package-lock.json: regenerated by the package manager
• package.json: Summary: This was a peer-dependency conflict (Fix pattern 2 — move the family together).

$0.09 of API usage, 10 turns, 128 s. report.json

Trial 2: green

Tests

Files changed

• package-lock.json: regenerated by the package manager
• package.json: `vitest` devDependency bumped from `^4.0.6` to `^5.0.0`.

$0.08 of API usage, 9 turns, 147 s. report.json

Trial 3: green

Tests

Files changed

• package-lock.json: regenerated by the package manager
• package.json: package.json**: Bumped `vitest` from `^4.0.6` to `^5.0.0` to match the `@vitest/coverage-v8@5.0.0` bump.

$0.08 of API usage, 10 turns, 153 s. report.json

What this is. These are real dependency-update pull requests from public repositories under permissive licenses, captured as they were: the base commit and the head commit. The agent that runs in a customer's own GitHub Actions ran against each one on our own machine, on our own Anthropic key. Nothing was pushed, commented or opened on anyone's repository. "Fixed" means the repository's own test suite passed before and after the change, flaky tests excluded by running the baseline more than once (three times in process, twice when run the way a press runs); it does not mean the change was reviewed by the maintainers or merged.