freckle / rcl

Stackage resolver changelog
MIT License
0 stars 0 forks source link

Differentiate cannot-find vs cannot-parse CHANGELOG #13

Closed pbrisbin closed 3 weeks ago

pbrisbin commented 3 years ago

There are 3 failure cases for CHANGELOG parsing:

  1. Doesn't exist
  2. Exists, but cannot find from/to version headers
  3. Exists, but somehow worked out an string

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.