Skip to content

fix(vscode): use the sst/opencode repository URL for Marketplace publishing - #55463

Merged
rekram1-node merged 1 commit into
devfrom
vscode-repo-url
Oct 14, 2026
Merged

rekram1-node merged 1 commit into
devfrom
vscode-repo-url

Conversation

@rekram1-node

@rekram1-node rekram1-node commented Oct 14, 2026 •

Copy link
Copy Markdown
Collaborator

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Publishing sst-dev.opencode fails because the VS Code Marketplace says the repository URL https://github.com/anomalyco/opencode.git is already used by another publisher.

This sets the extension's repository.url back to https://github.com/sst/opencode. That's the URL the published 0.0.13 used, sst-dev already owns it on the Marketplace, and GitHub redirects it to anomalyco/opencode.

How did you verify your code works?

The publish-vscode workflow for vscode-v1.0.0 packaged the extension and then failed at Marketplace publishing with the repository URL conflict. 0.0.13 published successfully with this URL.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Added by the opencode bot (AI-generated).

Related: #52455

@rekram1-node
rekram1-node merged commit 943dc00 into dev Oct 14, 2026
11 checks passed
@rekram1-node
rekram1-node deleted the vscode-repo-url branch October 14, 2026 16:04

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. This is a one-line manifest change, and nothing else in sdks/vscode or the publish-vscode workflow overrides repository.url, so the packaged VSIX will carry the sst/opencode URL. I couldn't confirm it end to end, because that needs a real Marketplace publish. Because script/publish runs with set -euo pipefail, a successful vsce publish should also let the Open VSX publish run again.

Public API: unchanged. This only changes extension manifest metadata.

No concerns.

Related: #52455

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