Skip to main content
Don’t want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you.
1

Create a weekly automation

Open app.devin.ai and navigate to Automations in the sidebar. Click Create automation and configure it:
  • Trigger: Expand Schedule and choose Every week — e.g., every Monday at 7:00 AM
  • Prompt: Paste the dependency update prompt below
If you use a Playbook for how your team handles dependency upgrades (e.g., always run npm run build after updating, or skip devDependencies), @-mention it in the automation’s prompt so every run follows the same process.
2

Add Knowledge to steer updates

Not every package should be updated automatically. Go to Settings → Resources → Knowledge and add entries that tell Devin what to skip or handle carefully:
  • Do not update react past v18 — we're mid-migration to v19 on a separate branch.
  • Always pin @types/node to match our Node.js version (20.x).
  • Skip eslint-plugin-import — it conflicts with our custom lint config.
  • Our test command is npm run test:ci, not npm test.
These Knowledge entries persist across every scheduled run, so Devin respects your constraints without you repeating them in the prompt.
3

Review what Devin delivers

Each Monday, Devin checks your repo for outdated packages and opens PRs on your behalf. A typical week might produce:PR #1 — Safe updates (patch + minor):
PR #2 — Major bump (separate, with notes):
Devin runs your test suite against each PR independently, so you can merge the safe batch immediately and take time reviewing the major bumps.
4

Iterate and expand

Once your weekly automation is running, you can refine it over time. Reply to any session it starts to give Devin follow-up instructions:Tips for keeping things smooth:
  • Separate frontend and backend — If your repo has both, create two automations so each PR stays focused and easy to review.
  • Let CI run fully before merging — Even safe-looking minor updates can introduce subtle bugs. Devin runs your tests, but your full CI pipeline adds another layer of confidence.
  • Check the automation on the Automations page to monitor run history, disable it during a code freeze, or adjust the schedule.