Source catalog
Which release-note sources have stable parsers today.
Stable parsers extract releases deterministically and don't incur per-poll LLM cost. Anything not on this list goes through the AI fallback parser; usable, but treat the results with more caution.
Supported sources
GitHub Releases
https://github.com/<owner>/<repo>: stable.
Pulls tagged releases via the GitHub API. Includes diff analysis between consecutive tags, risk scoring, and undocumented-change detection. The default and highest-coverage source, working for any public repo with tagged releases.
Google Ads API
https://developers.google.com/google-ads/api/docs/release-notes: stable.
Deterministic HTML adapter for the Google Ads API release-notes page. Each
v_x_y heading is treated as one release. Diff analysis is not applicable
for HTML changelog sources, so risk scoring on these releases is informational
rather than diff-derived.
VS Code Marketplace
https://marketplace.visualstudio.com/items?itemName=<publisher>.<extension>: stable.
Tracks a Visual Studio Code extension's published version history via the Marketplace gallery API. Each Marketplace version is treated as one release, using the extension's per-version changelog as the release notes. With editor extensions an increasingly active supply-chain target, tracking the extensions your team installs surfaces unexpected version bumps early. Diff analysis is not applicable, so risk scoring on these releases is informational. See Adding a VS Code extension for step-by-step instructions.
Open VSX Registry
https://open-vsx.org/extension/<namespace>/<name>: stable.
Tracks an extension on the vendor-neutral Open VSX Registry (used by VSCodium, Gitpod, Theia, and similar editors) via its public REST API. Behaves like the VS Code Marketplace adapter: one release per published version, changelog as the release notes, informational risk scoring. See Adding a VS Code extension for step-by-step instructions.
What if my source isn't listed? #
Two paths:
- Request a deterministic tracker (preferred). If a release-notes page is critical to your work, ask us to build a stable parser: no AI, no per-poll cost, reliable extraction. There's a Request a deterministic tracker button in the Add source modal when a URL routes to the fallback, and we prioritize by demand. See Reference → Parser stability.
- Try the AI fallback. Paste the URL when adding a source and opt in to the best-effort parser (a confirmation checkbox; its first sync uses AI allowance). For well-formatted single-page changelogs this works reasonably well. Some environments disable this path entirely, leaving only option 1.
This catalog grows as we ship adapters; check back periodically.
Frequently asked questions #
Which sources and ecosystems do you support? #
For release tracking: any GitHub repository with tagged releases, VS Code
extensions (Visual Studio Marketplace or Open VSX Registry), the Google Ads
API, and other release-notes / changelog pages via the
generic AI fallback parser. For
lockfile monitoring we parse npm
(package-lock.json), Yarn (yarn.lock), pnpm (pnpm-lock.yaml), Go
(go.sum), Rust (Cargo.lock), Python (poetry.lock, uv.lock,
Pipfile.lock, requirements.txt), and PHP (composer.lock).
Can I request support for a specific package ecosystem? #
Yes, email info@devupdate.io with your ecosystem request. We prioritise new ecosystems based on user demand.