Repository navigation
Deprecated extensions #1
Replies: 556 comments 864 replies
|
Nice feature! |
|
I like it as well :) Thanks! |
I can see how this flow works for full-on extension deprecation, but I do not have enough information to understand what the flow looks like for a deprecated setting. Isidor Nikolic (@isidorn) Can you please provide an overview of what this flow would look like? |
|
Eric Robinson (@ericdrobinson) good question. If an extension is deprecated in favour of a setting it would look like this |
|
Suggestion for deprecation due to no longer being maintained: tht13.gerrit-vscode As it's the first one that shows up in VS Code when searching for Gerrit, I suggest it to be marked as deprecated, especially because it no longer works. Also, please deprecate my fork: felipecrs.vscode-gerrit Although it works, I no longer maintain it. It's not a direct replacement, nor was it arranged, but if you want to suggest a replacement, there you go: SanderRonde.vscode--gerrit @SanderRonder is doing a great job in this new one. |
|
The extension heptio.jsonnet (repository) has been abandoned; there is a fork of it called Sebbia.jsonnetng (repository). |
|
Please deprecate https://marketplace.visualstudio.com/items?itemName=freebroccolo.reasonml - it was so popular in it's day that it remains the top hit when searching for It hasn't been updated in 3 years, when the readme was updated to say it's unmaintained: https://github.com/reasonml-editor/vscode-reasonml/blob/master/README.md The plugin the readme links to is also no longer maintained. I suggest https://marketplace.visualstudio.com/items?itemName=ocamllabs.ocaml-platform as the alternative extension to recommend instead. |
|
Hi, I'm the maintainer of vscode-github which is deprecated and should be replaced by GitHub Pull Requests and Issues. |
|
|
Hey! My Thanks for rolling out this feature! |
|
Please ensure to be open with the list of entries!
So... where it is actually maintained? Please post a link to a file. |
|
TSLint (deprecated) ( I have tried migrating from I'm aware that you want people to move to ESLint, and certainly not to start using TSLint at this point. However, I feel you should only deprecate an extension when the suggested replacement substantially replicates the functionality of the original without making changes to the user's wider environment. |
|
Hi I am the maintainer of HaaLeo.vscode-stylint. It is a linter extension for the unmaintained linter stylint and therefore should be deprecated in favor for stylelint.vscode-stylelint. Thx :) |
|
I have verified all the extensions that Felipe Santos (@felipecrs) scentoni Andrew Herron (@TheSpyder) Markus Wolf (@KnisterPeter) Anthony Fu (@antfu) Leo Hanisch (@HaaLeo) are indeed deprecated and have marked them as such. Simon Sobisch (@GitMensch) this is maintained on an internal CDN by the VS Code team as a short term solution. Soon the Marketplace will support this and then any extension author will be able to mark their extension as deprecated using the Marketplace UI.
Thank you very much ❤️ |
|
Hi, I would actually also consider the following Robot Framework Extensions as being deprecated:
Other deprecated Tools for Robot Framework:
Thanks! |
|
Please deprecate
I publish both under the The same deprecation is requested on Open VSX in EclipseFdn/publish-extensions#1191. |
|
Hi, please deprecate
I publish both under the |
|
Please deprecate rstack.rstest in favour of rstack.rstack.
I publish both under the rstack publisher. Please leave it installable rather than disallowing installs: not every user has updated yet. |
|
Hi! Please mark |
|
🤖 Sent by Prem Pillai's AI agent on his behalf. I am an Owner of the Block publisher (block). Please mark MCP Server (block.vscode-mcp-extension) as deprecated, without a recommended replacement. https://marketplace.visualstudio.com/items?itemName=block.vscode-mcp-extension The extension is already unpublished. Visual Studio Marketplace Support directed me to add this request here in their October 23 response to my existing removal-request email. Please coordinate any ownership verification through that email thread. This request applies only to block.vscode-mcp-extension. Thank you. |
|
Extension to deprecate: Fering.qsp and QSPFoundation.qsp-official Use instead (alternative extension): QSPFoundation.qsp-lsp I am the publisher of the deprecated extension (publisher: Reason: Development has moved to the new extension, QSPFoundation.qsp-lsp, maintained by the QSP Foundation in the official repository. These extensions have not been updated since 2024 and will receive no further updates. |
|
Please deprecate the following VS Code extension in favor of its replacement. Deprecated extension: Replacement extension: Reason: |
|
Please deprecate rstack.rslint in favour of rstack.rstack.
I publish both under the rstack publisher. Please leave it installable rather than disallowing installs: not every user has updated yet. |
|
Please deprecate
|
|
Please deprecate these two extensions in favour of their replacements. I publish all four under the
|
|
I'm the maintainer of Please deprecate it as it's no longer maintained. Karma itself is deprecated and I'm not aware of any replacement extensions to recommend. Deprecated: https://marketplace.visualstudio.com/items?itemName=lucono.karma-test-explorer |
|
Please deprecate
|
|
Coming soon: self-service extension deprecation in Visual Studio Marketplace We’re bringing extension deprecation directly to Marketplace. Publishers will be able to mark an extension as deprecated, indicate replacements to users, and manage that information themselves. A deprecated extension’s Marketplace page will remain accessible and display a notice to users on what to do next. Users in the VS Code client will see the same experience that exists today. The feature is not available yet. Please continue to submit deprecation requests in this discussion until we announce its launch. Existing VS Code deprecation entries will be carried over, so publishers should not need to recreate them. Read here for details. |
|
Please deprecate Claude Code Plus is the same extension under a new name and id. Version 1.0.22 of the old extension installs Claude Code Plus as a dependency. Please leave the old extension installable so existing users can receive that update. |
|
I am one of the maintainers for https://github.com/srcery-colors/srcery-vscode and it's extension. Today there is two other versions on the marketplace that is way out of date and not official. Can these be deprecated? |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We now support deprecating extensions.
An extension can be just deprecated or deprecated in favour of another extension or a setting. If a deprecated extension has this alternative extension or a setting the UI will guide users to migrate to the new extension or setting.
For now the extension will not be rendered as deprecated in the Marketplace. Support for this will come later.
In order to mark your extension as deprecated please reach out to us. You can also comment in this discussion.
If you know some extension which is deprecated you can also let us know and we will reach out to the respective extension author.
VS Code will not automatically migrate or uninstall deprecated extensions. Instead it will provide the following UI.
All reactions