User Story
"As a developer using a VS Code fork (Kiro, Cursor, or VSCodium), I want the quickmark extension to be available on the Open VSX Registry, so that I can install and update it directly from my editor's extension panel without manual VSIX workarounds."
The quickmark VS Code extension (ekropotin.vscode-quickmark) is currently only available on the Microsoft Visual Studio Marketplace. VS Code forks like Kiro, Cursor, and VSCodium use the Open VSX Registry instead, due to Microsoft's licensing restrictions on Marketplace access for non-Microsoft builds.
Would it be possible to also publish the extension on Open VSX? The process is documented at https://github.com/open-vsx/publish-extensions and typically involves adding a GitHub Action that publishes to both registries on release.
This would make quickmark available to a growing number of developers who use alternative VS Code-based editors while still benefiting from LSP-powered Markdown linting.
As a workaround, users can manually install the .vsix file, but automatic updates and discoverability via the extension panel are lost.
Thank you for the great tool — the Rust-based LSP approach is noticeably fast.
Acceptance Criteria
Additional Context
Microsoft's licensing restricts VS Code forks from accessing the official Marketplace (see eclipse/openvsx wiki). Editors like Kiro, Cursor, and VSCodium use Open VSX instead. Publishing there is documented at https://github.com/open-vsx/publish-extensions and typically involves adding ovsx publish to the existing release workflow.
As a workaround, users can currently download the .vsix manually and install via "Install from VSIX...", but they lose automatic updates and discoverability.
Priority
Medium
Code of Conduct
User Story
The quickmark VS Code extension (ekropotin.vscode-quickmark) is currently only available on the Microsoft Visual Studio Marketplace. VS Code forks like Kiro, Cursor, and VSCodium use the Open VSX Registry instead, due to Microsoft's licensing restrictions on Marketplace access for non-Microsoft builds.
Would it be possible to also publish the extension on Open VSX? The process is documented at https://github.com/open-vsx/publish-extensions and typically involves adding a GitHub Action that publishes to both registries on release.
This would make quickmark available to a growing number of developers who use alternative VS Code-based editors while still benefiting from LSP-powered Markdown linting.
As a workaround, users can manually install the .vsix file, but automatic updates and discoverability via the extension panel are lost.
Thank you for the great tool — the Rust-based LSP approach is noticeably fast.
Acceptance Criteria
Additional Context
Microsoft's licensing restricts VS Code forks from accessing the official Marketplace (see eclipse/openvsx wiki). Editors like Kiro, Cursor, and VSCodium use Open VSX instead. Publishing there is documented at https://github.com/open-vsx/publish-extensions and typically involves adding ovsx publish to the existing release workflow.
As a workaround, users can currently download the .vsix manually and install via "Install from VSIX...", but they lose automatic updates and discoverability.
Priority
Medium
Code of Conduct