On an eventNeeds a repository

Upgrade dependencies weekly

A PR, or needs_review

Once a week an agent bumps your dependencies, runs the tests and opens a pull request, or stops at needs_review and says why.

View .md

Best for

Repositories that fall behind on minor versions
A test suite that catches breaking upgrades

Uses

A connected GitHub repository
An automation with a schedule trigger

Automation · Weekly upgrades

POST /o/{org}/p/{project}/automations/{automation}/triggers

promptUpgrade dependencies to their latest minor versions, run the tests, and open a pull request listing each bump. Skip any upgrade that breaks the tests and say why.

{
  "kind": "schedule",
  "config": {
    "cron": "0 9 * * 1",
    "timezone": "UTC"
  }
}

Fig. The automation: its prompt, and the trigger that starts a run. Field names are the API's.

Watch it work, then read what comes back

GET /o/{org}/sessions/{session}/events

event: tool_usebash · bun outdated

event: tool_usebash · bun update

event: tool_result2 failed

event: thinkingzod 3.25 changed an error message the tests match.

event: messageOpened a pull request with 11 bumps; skipped zod.

Fig. The live stream while it works. Event names are the stream's.

GET /o/{org}/sessions/{session}

status: completed
branch: rush/weekly-upgrades
result: 11 upgrades, 1 skipped with the reason

Fig. The session when it ends. Field names are the API's.

Steps

01
Add a weekly schedule
A schedule trigger with cron set to the hour you want, in your timezone.
02
Read the pull request
Each bump is listed. An upgrade that breaks the tests is left out with its reason.