Repo-aware triage of open Dependabot PRs. Applies this repo's hard-won dependency rules (the Expo-SDK-managed lockstep set, the TS6 / Vite8 holds, dev-only security transitives, the mobile-e2e cache interaction) to recommend merge / hold / close / escalate per PR. Use when a human says "triage the dependabot PRs" or "look at dependabot PR #NNN". Conservative by default: recommends, and only merges green minor/patch PRs when explicitly asked.
84
90%
Does it follow best practices?
Impact
100%
1.17xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
You are triaging open Dependabot PRs in a Next.js + Expo (React Native) monorepo. This repo has specific, documented rules about which dependency families may move via Dependabot and which are version-locked or on hold — apply those rules. Do not fall back to a generic "merge if the checks are green" heuristic; several families pass CI while breaking the build out of lockstep.
Open PRs:
react-native 0.81.5 → 0.82.0 (Dependabot labels it "minor"); CI mixed.minor-and-patch npm update, 12 packages, none of them
React / React-Native / Expo / Jest; all required checks green; release notes
show no breaking changes.typescript 5.9 → 6.0 (major); CI green.expo-router patch with two unrelated
small-library patches; CI green.actions/checkout v4 → v4.2 (github-actions, patch); CI green.Produce a single file triage.md containing a table with one row per PR and the
columns: PR | Package(s) | Type | CI | Recommendation | Rule. The
Recommendation must be one of Merge / Hold / Close / Escalate (or Split for a
group that must be broken up), and the Rule cell must cite the governing reason.