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.
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.
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.
Source-reported evidence
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.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Trust and Retention, using evidence from Visual Studio Code Docs: Publishing Extensions as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.