This PR aims to tackle #58 as good as is possible without requiring the tag format to be additional metadata in the BCR, by requesting the Github API.
The procedure goes as follows:
Request endpoint for v-prefixed tag (most common)
If that is not successful request the endpoint for unprefixed tag
If neither are successful (or we have hit the Github rate limit), set the release format as "unknown"
For the v-prefixed and unprefixed tag formats, we can then link to the exact release notes. For the "unknown" format, we generate a link to the release search page.
Overall this should improve the experience a lot, as we never link the user to a 404 page, and only in rare cases (hitting the rate limit via extensive browsing + the release search page showing another release at the top) link to subpar information.
This PR aims to tackle #58 as good as is possible without requiring the tag format to be additional metadata in the BCR, by requesting the Github API.
The procedure goes as follows:
v
-prefixed tag (most common)For the v-prefixed and unprefixed tag formats, we can then link to the exact release notes. For the "unknown" format, we generate a link to the release search page.
Overall this should improve the experience a lot, as we never link the user to a 404 page, and only in rare cases (hitting the rate limit via extensive browsing + the release search page showing another release at the top) link to subpar information.
FIXES #58