Verifying major dependency bump safety
An AI agent opened a PR that bumps a transitive date-handling dependency two major versions to 'fix a deprecation warning,' adjusts three call sites it says were affected, and reports 'all tests pass.' CI is green. In a large TypeScript app with lots of date math, why is 'all tests pass' insufficient here, and how do you verify the bump is actually safe?
Implement
select_boundary_tests(call_sites: list[str], breaking_areas: list[str]) → list[str]Examples
in
[["src/billing.ts|parse,arith","src/report.ts|format","src/user.ts|timezone,parse"],["timezone","parse"]]out["src/billing.ts:parse","src/user.ts:timezone,parse"]in
[["src/billing.ts|parse,arith"],[]]out[]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.