<div dir="ltr"><div class="gmail_extra">[resend with correct cc]<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 18, 2015 at 8:42 AM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It would be nice if the github portgroup would default to only showing stable releases so that ports would not have to override livecheck.regex. There could be a switch ports could flip if they really want other versions. See the php 1.1 portgroup which has such a switch for ports hosted on pecl (php.pecl.prerelease yes). Though it might be harder to implement. The php 1.1 portgroup has it easy in that pecl tags each release as "beta" or "stable"; with github we might have to guess based on the format of the version number.<br>
</blockquote></div><br>GitHub does support marking releases as prereleases, but only for Git tags which have been annotated with release metadata via the GitHub site or API. (These are "releases" in the same sense as "github.tarball_from releases".) The GitHub API provides an endpoint (<a href="https://developer.github.com/v3/repos/releases/#get-the-latest-release">https://developer.github.com/v3/repos/releases/#get-the-latest-release</a>) that returns the most recent non-prerelease release. However, I don't know how many projects actually use the releases system, and I have also seen projects that forget to attach releases to some subset of their Git tags.<br><br></div><div class="gmail_extra">--Benjamin Gilbert<br><br></div></div>