Sorry if this has been covered somewhere, but I couldn’t find anything close either on the Forum or in Package Control docs.
Is there a way to prevent Package Control from upgrading a package to a beta release? I don’t want betas. However, I do want to update to finished packages.
Thank you.
Have the package developer:
- after the three numbers, following by a descriptor such as alpha, beta, build, etc.Example versions:
1.0.0
1.0.0-beta
1.0.0-build25
By default, Package Control will only install pre-releases if you set the install_prereleases setting (https://packagecontrol.io/docs/settings#setting-install_prereleases) with the name of the package you want pre-releases for.
My hunch is that developers not properly tagging pre-releases is most likely the issue.
Thanks for replying.
The upgrade is labelled in the description as beta. That is why I don’t want it.
It is a sub-version of version 3. I assume that the only solution is to remove the package.
I have no control over the package developers.
Well, you could open an issue with the developer and tell them about semver pre-releases.
Otherwise you’ll need to fork the package and decide which releases to tag yourself.
The last should be 1.0.0-build.25, otherwise 1.0.0-build3 would compare greater while 1.0.0-build.3 does not.
I have no idea how to do the latter, as I am not very familiar with Github. Opening an issue probably wouldn’t work also.
The simplest solution is to delete the package, which I have already done. I originally thought that there was a setting in Package Control that I could set, but I see that this is not the case.
Thank you for your input.