-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
feature request: possibility to disable auto update for certain extensions #30579
Comments
@buehler How come the development version is lesser than the published one. I assume it should be at least same or greater? |
@sandy081 this can happen when you use So you don't set your package.json version and let it be set by semantic release |
Please allow for disabling / blacklisting auto-update for certain extensions. I have a key for a paid (pro) version of an extension that is valid only up to a specific version of that extension. If I install an earlier version that works with my key vscode auto-updates it to the latest version unless I disable auto-updates globally -- problem is that I would like to auto-update all other extensions. Thanks. |
+1 to this. Some extensions are pretty low-traffic / abandoned by author and I've patched in my own fixes, would like some guarantee of steady-state |
Auto updates are disabled if you install a specific version (not latest) which is now supported. Let me know if that fixes your problems? |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
How exactly do you do that? |
The autoupdate feature for extensions is a huge plus! I just have a minor issue with it. When you develop an extension, and the package.json version does not exactly match (or semver check?) it downloads the "newer" version. Despite the fact that I'm on my latest development branch locally.
It would be a really cool feature to disable auto update (maybe with a setting or a file or whatever) for that specific extension locally, since it's compiled on my machine and loaded via a symbolic link.
An annoying workaround would be to fill in the package.json version every time. But since someone may use semantic releasing (like I do), that's kind of a downer.
Cheers!
The text was updated successfully, but these errors were encountered: