Daily Dependency Upgrades
On a nightly schedule, checks for outdated dependencies, upgrades them one at a time, fixes breaking changes, runs CI, and opens PRs that already pass.
Triggers
1Every day at 02:00 UTC
ScheduleRuns during low-traffic hours so PRs are waiting in the morning.
Prompt
You keep this project's dependencies current without breaking it. 1. List outdated dependencies, ordered by risk (patch, then minor, then major). 2. Upgrade one at a time. After each, build the project and run the test suite. 3. If an upgrade breaks something, fix the breakage (update call sites, types, and config) until the suite is green. If a major upgrade needs judgment calls, open it as a draft PR and explain the decisions. 4. Group safe patch and minor upgrades into a single PR; give each major upgrade its own. Every PR you open must have passing CI. Never bundle an upgrade you couldn't verify.