Getting started

DevUpdate.io watches release notes and the underlying git diffs for the libraries you depend on, so you can find out what actually changed before you update. This page walks you through the first three things to do once your account exists.

1. Add your first source #

A source is anything that publishes releases — typically a GitHub repository, but also static release-notes pages from vendors like Google. From the dashboard, open the Sources tab and click Add source. Paste the GitHub URL (https://github.com/<owner>/<repo>) and submit.

We immediately fetch the latest tagged releases via the GitHub API, queue diff analysis against the previous tag, and start polling for new releases on an hourly basis. The first summary usually appears within a minute.

2. Upload a lockfile (optional but powerful) #

Adding sources one-by-one is fine for a small set of libraries you care about. For everything in your project, it's faster to upload a lockfile — we read it, look up each package against its registry, and add the resolved repos as tracked sources in one go.

Open the Lockfiles tab and upload one of the supported formats: package-lock.json, yarn.lock, pnpm-lock.yaml, go.sum, Cargo.lock, poetry.lock, Pipfile.lock, requirements.txt, or composer.lock.

You'll get a checklist of discovered packages — pick which ones to start tracking. We'll cross-reference future updates against this lockfile so high-risk upgrades show up in your alerts.

3. Tune your digest #

Once releases are flowing, you probably don't want a notification for every patch. From Settings → Digests you can pick a daily or weekly schedule, choose your timezone, and decide what threshold counts as "worth emailing about."

What's next #

• Understand what shows up on the dashboard: Pulse feed.
• Learn how the risk number is computed: Risk scoring.
• Hook DevUpdate up to Claude or Cursor: MCP server.