Skip to main content
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

release-radar.nika

How it works

1

feed mode does the parsing

mode: feed turns RSS/Atom into structured items: no scraping, no XML wrangling. The extract: binding keeps just title/url/date.
2

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.
3

Silence is the feature

The digest runs when: size(...) > 0: nothing new, no model call, no noise. Schedule it daily and forget it.

Constructs you just used

Run it

What it needs: Network access to github.com for the feed, and a local model (Ollama serving qwen3.5:4b) for the digest.
1

Rehearse it

A mock model answers and nothing is written in your folder. Its network fetches still go out: a rehearsal replaces the model, not the tools. Before it runs, nika try names those hosts: may reach: github.com — the mock replaces the model, not the network. It stops at the approve gate, as a real run does.
2

Get your own copy

Save the file above as release-radar.nika in a new folder. It reads no sample file.
3

Check it, then run it

The run writes the state file out/release-radar.json.It asks at the approve gate before anything else runs. On a terminal you answer; in a script it pauses (exit 4) and prints the --resume line that continues it, or you answer up front with --answer approve=true.Any other model works: pass --model <provider>/<name> with its key, and cap a cloud model with --max-cost-usd.Run it twice: the first run reports every entry as new and writes the state, the second reports only what shipped in between.

Make it yours

  • Watch N dependencies: lift the feed URL into a list and for_each the 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.