Back to GrowthDex
Growth idea action plan

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.

rare tacticlow budget

Why this can grow a startup

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.

Company 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.

Source and metric

Source: Visual Studio Code Docs: Publishing Extensions

Verified publisher status requires six months of Marketplace history and a domain that is at least six months old; pre-release support requires engines.vscode >= 1.63.0.

TrustRetentionOperationsdeveloper toolsverified publisherrelease opsbeta channel
GrowthDex operator note

When to use it

Use this when Trust, Retention, Operations is relevant to developer tools, verified publisher, release ops and you can run a bounded test with a low budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Visual Studio Code Docs: Publishing Extensions and identify what is directly supported.
  2. Choose one channel context: Trust, Retention, Operations.
  3. Define the test around Verified publisher status requires six months of Marketplace history and a domain that is at least six months old; pre-release support requires engines.vscode >= 1.63.0..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian