New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical: Feature to install specific plugin versions. #1349
Comments
Title edits to try to sound less angry in the title :) But really frustrated by a key critical plugin that broke, and I can't work as a result. |
You're going a bit overboard with your "Critical" title prefix; this is clearly a feature request. But yes, I would very much appreciate pinning for packages. I'm in the same boat, being irritated by the updates that came with SublimeLinter 4 and would really prefer to stick with version 3. |
Hey kudos to new developers! I'm ok if they break things! (It's how we learn) ... but we always need backup options. In this case, there isn't one. Hence the "critical" :) Stuff that breaks and blocks us from using the (awesome!!) tool is pretty critical, no? |
This would also be very useful for testing. I could pin the version back and forth and see how the upgrade works. Something I just don't know how to do with current Package Control. |
You can't install particular versions currently, but you can more or less pin your currently installed version by just disabling auto updates for that package. Either way, duplicate of #938 |
This is critical for cases when key plugins are broken. SublimeLinter in particular has been pushing bad / broken updates, and won't run, but package control won't allow me to pin / install a specific version of a package that I know works.
The text was updated successfully, but these errors were encountered: