Watch sources¶
A watch names one upstream object, how often to look, and a policy. Sources only list versions; diffing and filtering happen in the core, so every source behaves the same way.
source |
Watches | Coordinates | Default scheme |
|---|---|---|---|
pypi |
a Python package | name |
pep440 |
npm |
an npm package, scoped or not | name |
semver |
crates |
a Rust crate | name |
semver |
github-release |
the releases of a GitHub repository | repo: owner/name |
semver |
github-tag |
the tags of a GitHub repository | repo: owner/name |
semver (lenient) |
gitlab-release |
the releases of a GitLab project | project |
semver |
Any of them can point at a private registry or mirror.
The shape of a watch¶
watches:
- name: fastapi # stable key: [a-z0-9][a-z0-9._-]*
source: pypi
coordinates: { name: fastapi }
interval: 30m # 5m to 720h, default 1h
scheme: pep440 # optional override
labels: # free routing keys for subscriptions
team: backend
policy:
prerelease: none
cooldown: 48h
Three ways to add one¶
Add it to the watch file and restart angelia serve --watches. The file is reconciled on startup: entries are
created, updated or deleted by name, in one transaction.
The add_watch tool takes the same keys. Give the agent a write token. See MCP.
Rate limits and coalescing¶
Each upstream host has its own token bucket, conditional requests are cached per target, and watches on the same object share one fetch. For GitHub, give Angelia a token so it gets 5,000 requests an hour instead of 60 (see GitHub).