Implement more flexible release detection
cbaines opened this issue · comments
Christopher Baines commented
Currently the logic for refreshing packages uses releases on GitHub, and then falls back to tags. Some apps have old release, and new tags, and for these apps, the package is just updated to the latest release on GitHub, and not the latest release tag [1].
At the moment, the value in the package updates is that the packages are at a version that you want to develop and test against, so its important that they are more up to date than this.
1: e.g. the Content Performance Manager