@dragestil There might be, but it appears to me that that the documentation is limited to the git logs, as I don't think the developer(s) made a detailed blog post about it or there was any news articles (as it seems few people knew that there was a public API, plus the only ones that really would have checked would be transport scheduling software developers).

My best guess is that adding support for Melbourne in the past only took a developer a few hours to figure out how the API worked and to convert the data to the right format for display, which is why Melbourne was previously supported, but years later the developer probably didn't want to do the same thing again, plus also have to update API tokens, so Melbourne support was dropped.