When a range isn't read yet
Why a comparison may fill in while you watch, and what the notices mean.
DepDelta reads a range's release notes the first time someone opens it. While it reads, the page shows "Fetching N releases from…" with a progress bar and fills in by itself. Once read, a range opens at once for everyone.
- Hourly limit
- Reading new ranges is limited per network address each hour, signed in or not. Ranges already read don't count. Settings shows how many are left and when the count resets. At the limit, the page shows what is already read.
- Releases without notes
- Some releases publish no notes. The page says which ones and links their commits, and the API diff still shows what changed in the code. Until something is known about them, the verdict is Unknown.
- Part of the range read
- "N of M releases aren't read yet" means the entries cover the rest. They fill in as reading goes on.
- Showing cached data
- A source didn't answer, so you see what DepDelta last read, with its date. Retry asks again.
- Yanked
- A withdrawn version, with the maintainer's reason and the version they point to instead.