chore: remove VS Code extension (marketplace blocked by Microsoft)#418
Merged
Conversation
Microsoft blocked the marketplace listing, so the bundled extension can't publish. Pull it from the repo and pipeline until that's resolved (git history preserves it for revival): - Delete extension/vscode-chippy/. - Remove the vscode-extension publish job from release.yml (goreleaser job is unaffected). - Remove the vscode-ext CI job from ci.yml. - Drop the npm extension entry from dependabot.yml. - Update docs (RELEASE.md, editors.md, quickstart.md, SECURITY.md) — DAP editor integration is unchanged; VS Code / Cursor still drive chippy via a `chippy -dap stdio` launch config (examples/dap/launch.json). The v1.3.0 binary release is unaffected (already shipped, 34 signed assets).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Microsoft blocked the marketplace listing for
Hidden-Pixel.vscode-chippy, so the bundled extension can no longer publish. Removing it from the repo and release pipeline until that resolves — git history preservesextension/vscode-chippy/for revival.Removed
extension/vscode-chippy/(the whole package).vscode-extensionpublish job inrelease.yml(the goreleaser job is independent and unaffected).vscode-exttest job inci.yml.dependabot.yml(stops the@types/vscodedrift that broke the v1.3.0 publish).Docs
docs/editors.md,docs/quickstart.md— VS Code / Cursor now documented as DAP-via-launch-config (chippy -dap stdio,examples/dap/launch.json); no bundled extension.docs/RELEASE.md— dropped the "publishes the VS Code extension" step.SECURITY.md— dependabot now tracks Go + Actions only.docs/context.md— removal note added; historical merged-PR entries left intact.Unaffected
.vsixis gone.Validated: all three workflow/dependabot YAMLs parse; no
extension/vscodereferences remain outside the generated CHANGELOG and historical context.md log;go build ./...clean.