Reliable Daily Changelog Diffs in 3 Steps (Before Semantic Duplicate Alerts)

Description and use

A scheduled scraper normalizes changelog text, compares it to a durable snapshot, and notifies with a diff, reducing false positives and speeding operator response.

Problem

On-call teams receive vague, late alerts when a daily changelog page changes, making it hard to determine if a record‑deduplication index is stale.

Outcome

The pipeline reduces false positives, delivers timely diff notifications, and preserves a durable baseline for comparison.

Workflow

• Schedule a scrape of the changelog page
• Fetch page content via Infrai API or direct HTTP
• Normalize text: strip tags, unescape entities, remove ISO timestamps, collapse whitespace
• Compute hash of normalized content
• Compare hash to durable snapshot; if unchanged, exit
• If changed, compute line‑oriented diff of normalized text
• Atomically replace snapshot file
• Send notification containing diff lines

Evidence

scrape the page on a schedule, normalize unstable text, compare it with a durable previous snapshot, and notify with the diff rather than the whole page

Source

The snapshot has to survive a deployment. An in-memory lastSeen value guarantees a false alarm after every restart

Source

It first checks the public Infrai discovery document for the declared scrape path

Source