It would be good to still link to the full CHANGELOG in the case of (2).
(It's unclear if (3) is actually an empty file, there may still be no reason to link for that, but I also don't mind if we do.)
For example, comparing lts-16.29 to lts-17.1 updates base-4.13.0.0 to base-4.14.1.0. We can find the CHANGELOG, but there's no heading for that version, so we show nothing in RCL.
There are 3 failure cases for CHANGELOG parsing:
It would be good to still link to the full CHANGELOG in the case of (2).
(It's unclear if (3) is actually an empty file, there may still be no reason to link for that, but I also don't mind if we do.)
For example, comparing
lts-16.29
tolts-17.1
updatesbase-4.13.0.0
tobase-4.14.1.0
. We can find the CHANGELOG, but there's no heading for that version, so we show nothing in RCL.