# VS Code extension verified publisher and pre-release track

> Earn the verified publisher badge, then use the built-in pre-release track for sharper feedback instead of surprising the stable install base.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/vs-code-extension-verified-publisher-and-pre-release-track/
- Source: [code.visualstudio.com](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)
- GrowthDex source hub: [Visual Studio Code Docs: Publishing Extensions](/sources/visual-studio-code-docs-publishing-extensions-code-visualstudio-com/)
- Last checked: 2026-06-06T12:40:00Z
- Rarity: rare
- Budget: low
- Channels: Trust, Retention, Operations
- Stages: developer tools, verified publisher, release ops, beta channel


## Why this can grow

A lot of extension teams mix two different jobs together: proving who they are and testing what is new. VS Code gives a cleaner split. Verified publisher status adds a trust signal tied to domain ownership and time in good standing, while the pre-release channel gives risk-tolerant users a place to try newer builds. The pre-release rules are specific enough to matter operationally: version numbers must stay distinct, pre-release support starts at VS Code 1.63.0, and the docs recommend odd and even release tracks. That makes experimentation feel deliberate instead of chaotic.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where vs code extension verified publisher and pre-release track can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Trust and Retention channel.
3. Use the evidence from code.visualstudio.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

VS Code's publishing guide says verified publisher status requires at least one Marketplace extension for six months and a domain registration that is also at least six months old. The same guide says pre-release extensions should use the --pre-release flag, keep distinct versions, and set engines.vscode to >= 1.63.0.

## Adjacent tactics in the same lane

- [VS Code extension README and CHANGELOG finish the detail page](/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/) - same source, 1 shared channel, 1 shared stage
- [Chrome Web Store partial rollout after 10,000 active users](/growth-ideas/chrome-web-store-partial-rollout-after-10000-active-users/) - 2 shared channels
- [Firefox approved-version rollback within 24 hours](/growth-ideas/firefox-approved-version-rollback-within-24-hours/) - 2 shared channels
- [JetBrains plugin hidden release before public launch](/growth-ideas/jetbrains-plugin-hidden-release-before-public-launch/) - 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The VS Code extension page should finish the trust check](/blog/the-vs-code-extension-page-should-finish-the-trust-check/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.