All Platforms
VS Code releases & version history
Apps & Browsers
Latest: 1.109.5
17
Releases
3
Articles
30
Supported
VS Code Version Timeline
Live data1.109v1.109.5
Released: Feb 4, 2026
Supported
1.108v1.108.2
Released: Jan 8, 2026
Supported
1.107v1.107.1
Released: Dec 10, 2025
Supported
1.106v1.106.3
Released: Nov 12, 2025
Supported
1.105v1.105.1
Released: Oct 9, 2025
Supported
1.104v1.104.3
Released: Sep 11, 2025
Supported
1.103v1.103.2
Released: Aug 7, 2025
Supported
1.102v1.102.3
Released: Jul 10, 2025
Supported
1.101v1.101.2
Released: Jun 12, 2025
Supported
1.100v1.100.3
Released: May 8, 2025
Supported
1.98v1.98.2
Released: Mar 5, 2025
Supported
1.97v1.97.2
Released: Feb 6, 2025
Supported
1.96v1.96.4
Released: Dec 11, 2024
Supported
1.95v1.95.3
Released: Oct 29, 2024
Supported
1.94v1.94.2
Released: Oct 3, 2024
Supported
1.93v1.93.1
Released: Sep 5, 2024
Supported
1.92v1.92.2
Released: Aug 1, 2024
Supported
1.91v1.91.1
Released: Jul 3, 2024
Supported
1.90v1.90.2
Released: Jun 5, 2024
Supported
1.89v1.89.1
Released: May 2, 2024
Supported
1.87v1.87.2
Released: Feb 28, 2024
Supported
1.86v1.86.2
Released: Feb 1, 2024
Supported
1.85v1.85.2
Released: Dec 7, 2023
Supported
1.84v1.84.2
Released: Nov 1, 2023
Supported
1.83v1.83.1
Released: Oct 4, 2023
Supported
1.82v1.82.3
Released: Sep 7, 2023
Supported
1.81v1.81.1
Released: Aug 3, 2023
Supported
1.80v1.80.2
Released: Jul 6, 2023
Supported
1.79v1.79.2
Released: Jun 8, 2023
Supported
1.78v1.78.2
Released: May 3, 2023
Supported
Data Collection Methodology
Data Collection Methodology
Version & Lifecycle Data
Version data from GitHub Releases API (microsoft/vscode), refreshed every 6 hours.
How Teams Use This Data
Enterprise Rollouts
Enterprise teams track VS Code releases to verify extension compatibility before updating.
Help Us Improve This Data
Found an inaccuracy or have a correction? We review all community feedback to maintain data quality.
Maintained by the ReleaseRun Team
This page is maintained by platform engineers who have collectively managed hundreds of VS Code deployments across production environments. We aggregate and verify data from official sources to help teams make informed upgrade decisions.
Updated daily
Verified data
Related Articles
Latest guides
VS Code 1.109.0 Release Notes: Claude Agents, Integrated Browser, and the Stuff People Actually Mention
Feb 10, 2026
VS Code 1.108.2 release notes: the recovery build you install when 1.108 acts weird
Jan 29, 2026
VS Code 1.108.0 release notes: housekeeping, real changes, and a sane upgrade plan
Jan 13, 2026
Quick Reference
Key Dates
- Latest Version: See timeline below
- Release Cycle: Monthly
Best Practices
- Validate extension compatibility before broad rollout
- Pin or stage updates for managed developer environments
Official Resources
Complete VS Code Version Timeline
We track 17 VS Code releases. The latest version is 1.109.5.
VS Code is Microsoft's free code editor with monthly releases. This page tracks all VS Code versions, helping teams manage extension compatibility and adopt new editor features.
Visual Studio Code releases continue to shape modern development workflows, with Microsoft shipping monthly updates that introduce features impacting millions of developers worldwide. This complete VS Code release history tracks every version from VS Code’s public launch, documenting feature additions, performance improvements, and breaking changes that matter to frontend developers, backend engineers, and DevOps teams. Whether you’re managing extension compatibility, planning IDE upgrades across your organization, or staying ahead of deprecated APIs, this timeline provides the version intelligence you need.
Since its 2015 debut, VS Code has evolved from a lightweight code editor into the dominant development environment across JavaScript, TypeScript, Python, Go, and dozens of other languages. Each monthly release—numbered using semantic versioning (major.minor.patch)—brings new language server protocol improvements, debugger enhancements, and editor capabilities that directly affect your daily coding experience.
Why Track VS Code Releases?
Stay Compatible with Extension Ecosystems
VS Code’s extension API evolves with each release. Tracking version changes helps you understand when proposed APIs become stable, when deprecated features will be removed, and how new capabilities affect your extension dependencies. Avoid runtime errors and compatibility breaks by knowing exactly what changed between your current version and the latest release.
VS Code’s extension API evolves with each release. Tracking version changes helps you understand when proposed APIs become stable, when deprecated features will be removed, and how new capabilities affect your extension dependencies. Avoid runtime errors and compatibility breaks by knowing exactly what changed between your current version and the latest release.
Plan Enterprise Rollouts with Confidence
Organizations managing hundreds or thousands of developer workstations need advance notice of breaking changes. Our release guides identify when workspace settings change structure, when language server protocols update, or when new security policies affect corporate environments – giving IT teams the lead time needed for testing and gradual deployment.
Organizations managing hundreds or thousands of developer workstations need advance notice of breaking changes. Our release guides identify when workspace settings change structure, when language server protocols update, or when new security policies affect corporate environments – giving IT teams the lead time needed for testing and gradual deployment.
Optimize Development Workflows
New VS Code releases frequently introduce productivity features that can eliminate entire categories of manual work: improved IntelliSense algorithms, faster search implementations, better Git integration, enhanced debugging tools. By tracking releases systematically, you discover workflow optimizations months before they appear in blog posts or tutorials.
New VS Code releases frequently introduce productivity features that can eliminate entire categories of manual work: improved IntelliSense algorithms, faster search implementations, better Git integration, enhanced debugging tools. By tracking releases systematically, you discover workflow optimizations months before they appear in blog posts or tutorials.
Debug Version-Specific Issues
When a colleague reports “VS Code isn’t working,” knowing their exact version number and comparing it against release notes helps you diagnose whether they’ve hit a known bug, missed a critical patch, or need to downgrade temporarily. This release history serves as your diagnostic reference when troubleshooting editor behavior.
When a colleague reports “VS Code isn’t working,” knowing their exact version number and comparing it against release notes helps you diagnose whether they’ve hit a known bug, missed a critical patch, or need to downgrade temporarily. This release history serves as your diagnostic reference when troubleshooting editor behavior.
Use Cases: Who Uses This Release History?
Extension Developers
Track proposed API graduations, understand when vscode.d.ts type definitions change, and plan extension updates around breaking changes. Our release guides highlight Extension API changes in dedicated sections so you can maintain compatibility across VS Code versions.
Track proposed API graduations, understand when vscode.d.ts type definitions change, and plan extension updates around breaking changes. Our release guides highlight Extension API changes in dedicated sections so you can maintain compatibility across VS Code versions.
Development Team Leads
Make informed decisions about when to mandate IDE upgrades across your team. Understand which releases fix critical bugs affecting your language stack (Python, Go, Rust, etc.) versus which introduce experimental features that can wait.
Make informed decisions about when to mandate IDE upgrades across your team. Understand which releases fix critical bugs affecting your language stack (Python, Go, Rust, etc.) versus which introduce experimental features that can wait.
DevOps Engineers
Automate VS Code deployments with confidence. Know which versions introduce new CLI flags, change settings.json schema, or affect remote development scenarios (SSH, containers, WSL2). Our guides document these infrastructure-relevant changes explicitly.
Automate VS Code deployments with confidence. Know which versions introduce new CLI flags, change settings.json schema, or affect remote development scenarios (SSH, containers, WSL2). Our guides document these infrastructure-relevant changes explicitly.
Technical Writers
Maintain accurate documentation that references specific VS Code versions. When writing tutorials or setup guides, cite exact version numbers and feature availability using our historical timeline as your source of truth.
Maintain accurate documentation that references specific VS Code versions. When writing tutorials or setup guides, cite exact version numbers and feature availability using our historical timeline as your source of truth.
Open Source Maintainers
Understand how VS Code’s language server protocol updates affect your LSP implementation. Track when new diagnostic capabilities, semantic token types, or code action kinds become available in stable releases.
Understand how VS Code’s language server protocol updates affect your LSP implementation. Track when new diagnostic capabilities, semantic token types, or code action kinds become available in stable releases.
FAQ’s
How often does VS Code release new versions?
VS Code follows a monthly release cycle, with stable versions typically released during the first week of each month. Additionally, Microsoft ships daily Insiders builds for early testing of upcoming features. Each monthly stable release increments the minor version number (e.g., 1.85.0 → 1.86.0).
VS Code follows a monthly release cycle, with stable versions typically released during the first week of each month. Additionally, Microsoft ships daily Insiders builds for early testing of upcoming features. Each monthly stable release increments the minor version number (e.g., 1.85.0 → 1.86.0).
What’s the difference between Stable, Insiders, and Exploration builds?
Stable releases are production-ready versions updated monthly. Insiders builds are daily releases containing features scheduled for the next stable version, useful for testing but potentially unstable. Exploration builds are experimental branches testing architectural changes. This hub tracks Stable and major Insiders milestones.
Stable releases are production-ready versions updated monthly. Insiders builds are daily releases containing features scheduled for the next stable version, useful for testing but potentially unstable. Exploration builds are experimental branches testing architectural changes. This hub tracks Stable and major Insiders milestones.
Are older VS Code versions still available for download?
Yes. Microsoft maintains an archive of previous stable releases at
Yes. Microsoft maintains an archive of previous stable releases at
https://code.visualstudio.com/updates. Specific version downloads are available for Windows, macOS, and Linux. Our release guide articles link directly to official download pages for each tracked version.How do I know if I should upgrade to the latest VS Code release?
Check our release guide for the version you’re considering. We provide “Upgrade Recommendation” sections that flag whether a release contains critical security fixes (upgrade immediately), breaking changes (test first), or primarily minor improvements (safe to delay). High-priority releases are tagged accordingly.
Check our release guide for the version you’re considering. We provide “Upgrade Recommendation” sections that flag whether a release contains critical security fixes (upgrade immediately), breaking changes (test first), or primarily minor improvements (safe to delay). High-priority releases are tagged accordingly.
Does VS Code support multiple versions installed simultaneously?
Yes, through portable mode or by installing Stable and Insiders side-by-side. This allows testing new versions without affecting your production environment. Our guides include instructions for managing multiple installations when version-specific testing is necessary.
Yes, through portable mode or by installing Stable and Insiders side-by-side. This allows testing new versions without affecting your production environment. Our guides include instructions for managing multiple installations when version-specific testing is necessary.
What does “Extension API Finalization” mean in release notes?
VS Code introduces new extension capabilities as “proposed APIs” that can change based on feedback. When an API is “finalized,” it moves from proposed to stable, meaning extension developers can use it in production extensions without requiring special flags. Our guides track these API graduations explicitly.
VS Code introduces new extension capabilities as “proposed APIs” that can change based on feedback. When an API is “finalized,” it moves from proposed to stable, meaning extension developers can use it in production extensions without requiring special flags. Our guides track these API graduations explicitly.
Where does ReleaseRun get VS Code release data?
We aggregate data from the official VS Code GitHub releases (https://github.com/microsoft/vscode/releases), Microsoft’s update blog (https://code.visualstudio.com/updates), and extension API documentation. Each release guide cites original sources and links to official changelogs.
We aggregate data from the official VS Code GitHub releases (https://github.com/microsoft/vscode/releases), Microsoft’s update blog (https://code.visualstudio.com/updates), and extension API documentation. Each release guide cites original sources and links to official changelogs.
How detailed are ReleaseRun’s VS Code release guides?
Our guides average 1000 words and include: comprehensive “What Changed” analysis, feature breakdowns with use case examples, breaking change documentation, extension API updates, upgrade recommendations by user type, and troubleshooting notes for known issues. They’re designed for developers who need more context than raw changelog entries provide.
Our guides average 1000 words and include: comprehensive “What Changed” analysis, feature breakdowns with use case examples, breaking change documentation, extension API updates, upgrade recommendations by user type, and troubleshooting notes for known issues. They’re designed for developers who need more context than raw changelog entries provide.
Resources
Official VS Code Resources
- VS Code Release Notes – Microsoft’s official monthly update announcements
- GitHub Releases – Technical release tags and downloadable builds
- Extension API Changes – Documentation for extension developers
- VS Code Roadmap – Upcoming feature plans and development priorities
How ReleaseRun Complements Official Documentation
Microsoft’s release notes are comprehensive but optimized for users already familiar with VS Code’s architecture. ReleaseRun release guides translate technical changes into business impact: we explain why a new language server protocol version matters, who should prioritize an upgrade, and how specific changes affect real-world development workflows. Our guides serve as interpretive layer between raw changelogs and actionable developer intelligence.
Microsoft’s release notes are comprehensive but optimized for users already familiar with VS Code’s architecture. ReleaseRun release guides translate technical changes into business impact: we explain why a new language server protocol version matters, who should prioritize an upgrade, and how specific changes affect real-world development workflows. Our guides serve as interpretive layer between raw changelogs and actionable developer intelligence.
Get VS Code Release History Release Alerts
Breaking changes, security patches, and EOL warnings — delivered monthly.
Frequently Asked Questions
How often does VS Code release?
VS Code typically ships a new stable release every month, with occasional recovery or patch updates.
Does VS Code auto-update?
Yes. VS Code auto-updates by default on desktop installations, though enterprise environments often control update timing.