Compatibility and repairs · Every plan
David
David’s job is to find what upstream changes, deprecations and end-of-life dates mean for the company’s code, and report the repair pull requests that fix them.
On this page
What David does
- Upstream releases, breaking or removed APIs and deprecations that affect the code
- Dependency versions and pins, and the repository’s dependency index
- The repository map: how the code is laid out and what depends on what
- Runtime versions pinned in workflows, images and templates, with their end-of-life datesPro
- Repair pull requests for supported fixes, opened as drafts
- New and upgraded packages checked on each merged pull request, and a quarterly licence reportStudio
What you can ask
You ask Grant, and he brings in David for questions like these. On Free, he answers from David’s saved briefs.
- “Does the latest Node.js release break anything in our repositories?”
- “Which repair pull requests are waiting for review?”
- “What in our code depends on the package that was just deprecated?”
- “Did anything risky enter our dependencies this week?”Studio
What you get
Next.js 16 removes the legacy image loader, which apps/web uses in two files. A draft repair pull request (#412) moves both to the new loader and is waiting for review. Nothing merges until you do.
What David reads
- World State changes
- Repository context
- GitHub deliveryStudio
When David works
At each scheduled check-in, on pushes and repository impact updates and when you ask Grant. On Free, only at the monthly check-in you start.
What David may do
Reports repair PRs; supported fixes arrive as drafts. Nothing merges or deploys.
What David never does
- Merge, deploy or close a pull request
- Ask for a new repair from a check-in
- Treat a draft pull request as a fix that is in place
- Install or run a package
- Say what a licence allows or whether the company complies
