T2 chain · devops / dependency hygiene — mode: feed parses
RSS/Atom natively, and the state-file pattern (read last run →
diff → write next state) means you only hear about what’s new.
The job
« Did anything we depend on ship this week? » Checking releases pages is a robot’s job. This workflow reads the Atom feed, diffs it against what it saw last run (RFC 6902 — empty patch means silence), digests only the new entries, and saves the state for next time. First run? The missing state file recovers to an empty list.The shape
The file
t2-release-radar.nika.yaml
How it works
feed mode does the parsing
mode: feed turns RSS/Atom into structured items — no scraping,
no XML wrangling. The output: binding keeps just title/url/date.State makes it incremental
previous reads the state file (recovering to [] on first run) ·
nika:json_diff against the fresh feed yields ONLY the new
entries · save_state overwrites for next time.Constructs you just used
| Construct | Where | Reference |
|---|---|---|
nika:fetch mode: feed | feed | Builtins |
| state-file pattern | previous · save_state | Bindings |
nika:json_diff (RFC 6902) | fresh | Builtins |
on_error: recover: first-run | previous | Error model |
Make it yours
- Watch N dependencies: lift the feed URL into a list and
for_eachthe fetch (Competitor radar shows the leash). - Pipe breaking-change suspects into PR review fan-out’s reviewer prompt.
- Swap the feed for your vendor’s changelog RSS — the shape doesn’t change.
Next · Resume screener
PII never leaves the machine — a local-model rubric per candidate,
ranked deterministically.