Skip to content

Microsoft VS Code only: drop the other editors' paths - #28

Merged
aledbf merged 1 commit into
mainfrom
vscode-only
Nov 12, 2026
Merged

aledbf merged 1 commit into
mainfrom
vscode-only

Conversation

@aledbf

@aledbf aledbf commented Nov 12, 2026

Copy link
Copy Markdown
Member

Part of #24. Spinbox targets Microsoft VS Code stable only, so this removes what existed for other editors:

  • Remote-SSH is ms-vscode-remote.remote-ssh alone. Gone: jeanp413.open-remote-ssh, REMOTE_EXTENSIONS, remoteExtensionForEditor and its appName check. A new test checks that an installed open-remote-ssh no longer counts: Spinbox offers Microsoft's.
  • Open VSX publishing is gone, since only other editors read it: task publish:openvsx, its step and OVSX_PAT in publish.yml, the ovsx devDependency (lockfile through sfw), and the Open VSX steps 3 and 5 in docs/publishing.md. Its steps are renumbered and CONTRIBUTING's link is updated. Spinbox is still published to the Marketplace, the GitHub release and ghcr (spin vscode install).
  • README: Microsoft VS Code 1.146 and Microsoft's Remote-SSH.

Planted bug: accepting jeanp413.open-remote-ssh as installed turned the new test red; reverted with Edit.

If an Open VSX namespace or the OVSX_PAT environment secret was ever set up, it is now unused and can be removed by hand.

🤖 Generated with Claude Code

Spinbox targets Microsoft VS Code stable alone. So Remote-SSH is Microsoft's
ms-vscode-remote.remote-ssh, with no jeanp413.open-remote-ssh fallback and no
appName check for which marketplace an editor reads; and the extension is
published to the Visual Studio Marketplace, the GitHub release and ghcr, no
longer to Open VSX, which only other editors read: publish:openvsx, its
workflow step and OVSX_PAT, the ovsx dependency, and the Open VSX account
steps in docs/publishing.md go.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit dd3b67d into main Nov 12, 2026
3 checks passed
@aledbf
aledbf deleted the vscode-only branch November 12, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant