VS Marketplace Publishing

[ChrisonSimtian]

• Publish an extension to VS Marketplace
• Become a trusted publisher
• reserve fallout namespace

[ChrisonSimtian]

MS came back to me today:

Hello,

We are from VS Marketplace Support Team. This mail is regarding your publisher domain, our VS Marketplace policy requires that the extensions need more than 6-month track record of demonstrating extension-relevant content, trust and positive reputation. Since your extensions have been available for less than six months, we kindly request that you resubmit the domain verification after completing the six-month period based on the published date. This will allow us to finalize the approval and notify you accordingly. We appreciate your patience. Thank you for applying to become a trusted publisher.

Regards,
VS Marketplace Support Team

[ChrisonSimtian]

🤖 AI-generated working note — TODO for the AI continuing this, not a human-facing spec.

PoC branch: ChrisonSimtian/Fallout@feature/vscode-extension-poc (builds green on current main).

Decided

• Version 2026.<minor>.<patch>: major.minor track the framework; patch = NBGV height scoped to poc/vscode-fallout/ (own version.json, pathFilters: [":/poc/vscode-fallout"]). No manual package.json bumps.
• Channels: pre-release from main (--pre-release), stable from release/YYYY. Separated by minor (main runs a minor ahead) → no odd/even hack needed.
• Two feeds, package once → push both: VS Code Marketplace (vsce) + Open VSX (ovsx).
• Dogfood: CI calls dotnet fallout PublishVsCodeExtension, not hand-rolled npm in the workflow (mirror preview.yml → dotnet fallout Publish).
• Secrets: VSCE_PAT, OVSX_PAT (added to fork Actions secrets).
• Icon: .assets/fallout-logo.png; derive a ≥128px variant into .assets/ if the source needs resizing.

TODO

• poc/vscode-fallout/version.json (path-scoped NBGV); PackVsCodeExtension derives version via nbgv get-version instead of reading package.json.
• package.json: real publisher, drop "private": true, add icon + marketplace metadata.
• PublishVsCodeExtension target: consumes packed vsix; [Secret] VsceToken/OvsxToken, bool PreRelease, Requires(Host is GitHubActions); runs vsce publish + ovsx publish.
• CI lane (vscode-extension.yml, + actions/setup-node): main → pre-release, tag/release/* → stable; both via the Fallout target.

Blocked / needs human

• Chris to provide MS Marketplace publisher ID + Open VSX namespace — left blank in package.json until then.
• Note: MS reply above = domain verification (verified badge), ~6mo wait. Does not block publishing — unverified publish works now; Open VSX has no such gate.

[ChrisonSimtian]

🤖 AI-generated update — progress + handoff state.

Done since last note

• ✅ Logo tracked + wired as marketplace icon. .assets/fallout-logo.png (387×387) → copied to icon.png at pack time (mirrors the LICENSE pattern, gitignored). Verified: vsce package ships extension/icon.png. Commit 49d53f02.

Branch state (continue here): ChrisonSimtian/Fallout@feature/vscode-extension-poc @ 49d53f02, rebased on current fork/main, builds green. Pull this before resuming on another machine.

Remaining TODO unchanged (see note above): path-scoped version.json, package.json publisher/metadata + drop "private": true, PublishVsCodeExtension target, CI lane via dotnet fallout.

Still needs human: Chris to provide MS Marketplace publisher ID + Open VSX namespace.