Hi,
> It is possible to write watch files dealing with pre-releases without using > fakeupstream.cgi. Here are some variants: > ... > > The 'failure scenario' describes just one of many mistakes upstream can make, > and fakeupstream.cgi isn't meant to correct such upstream human mistakes. It > is > rather meant to make it possible to track upstream versions where it otherwise > would not be. In 'failure scenario', I admire that it maybe a rare case, the problem is that tag itself doesn't have information whether pre-release or official release. (need to contains the identifier to distingish) Thus, suggested watch rule works in most cases if upstream tagged as pre-release to v0.1.97pre or something, but it will not work as expectedlly if v0.1.97 tag is given to pre-release. (it is bad practice, though) In GitHub, pre-release requires tag, so it may happen re-creating same tag for release from a sysytem point of view. Anyway, it may be a trivial exceptional case, so I'll close it. Regards,
