wbond / packagecontrol.io

The Package Control website
https://packagecontrol.io
Other
111 stars 46 forks source link

Packages display incorrect Sublime Text version markers #113

Closed OdatNurd closed 4 years ago

OdatNurd commented 4 years ago

In various places on packagecontrol.io, packages are "tagged" with the version of Sublime that they support, such as ST2 , ST3 or ST2/ST3 on actual package pages, 3 on the front page if they support Sublime Text 3 only, and ST2 or ST3 on search result pages if they support only one version or the other.

In some cases, the information in these tags is incorrect, with packages being marked as supporting both versions when in fact they only support one.

Since knowing this generally requires peering into the channel file to see the version requirements declared there, the only package I'm personally aware of that is a demonstration of this is the OverrideAudit package.

The releases key for this package (found in this repository file) is:

"releases": [
    {
        "sublime_text": "3092 - 3196",
        "tags": "legacy-v"
    },
    {
        "sublime_text": ">=3197",
        "tags": true
    }
]

The intent here is that the 1.x series supports only versions of Sublime Text 3 prior to build 3197 (but with a minimum cap) while a newer 2.x series requires Sublime 3197 or greater.

Prior to the version split seen here, the minimum requirement was >=3092 and at that point the package was marked as being ST3 only. However it now is marked as ST2/ST3 even though the version ranges that it supports are still Sublime Text 3 only.