Problem
The RELEASE protocol (codev/protocols/release/protocol.md) bumps the VS Code extension version (via pnpm bump-version → bump-vscode.sh) but has no step that publishes the extension to the Marketplace. Consequence observed 2026-07-27: the v3.2.4 release shipped npm packages and release notes promising extension 3.2.4, but the Marketplace still serves 3.2.3.
Fix
Add a publish step to the protocol after npm publish (step 7): npx @vscode/vsce publish from apps/vscode (the existing vscode:prepublish script already builds the dep graph). Document the PAT requirement — the publisher PAT is not stored in the repo/env; the human runs or supplies it. Also add a verification line (query the Marketplace for the new version) and note that pre-release versions skip this step entirely (Marketplace rejects semver pre-release suffixes, matching bump-vscode.sh behavior).
Also
Catch up the Marketplace to the current release (3.2.4 or whatever is current when this lands) as part of the fix's verification.
Problem
The RELEASE protocol (
codev/protocols/release/protocol.md) bumps the VS Code extension version (viapnpm bump-version→bump-vscode.sh) but has no step that publishes the extension to the Marketplace. Consequence observed 2026-07-27: the v3.2.4 release shipped npm packages and release notes promising extension3.2.4, but the Marketplace still serves3.2.3.Fix
Add a publish step to the protocol after npm publish (step 7):
npx @vscode/vsce publishfromapps/vscode(the existingvscode:prepublishscript already builds the dep graph). Document the PAT requirement — the publisher PAT is not stored in the repo/env; the human runs or supplies it. Also add a verification line (query the Marketplace for the new version) and note that pre-release versions skip this step entirely (Marketplace rejects semver pre-release suffixes, matching bump-vscode.sh behavior).Also
Catch up the Marketplace to the current release (3.2.4 or whatever is current when this lands) as part of the fix's verification.