Text of code.visualstudio.com › updates › v1_69 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

June 2022 (version 1.69)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. June 2022 (version 1.69) Update 1.69.1 : The update addresses these issues . Update 1.69.2 : The update addresses these issues . Downloads for 1.69.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the June 2022 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include: 3-way merge editor - Resolve merge conflicts within VS Code.

Command Center - New UI to search files, run commands, and navigate cursor history. Do Not Disturb mode - Silence non-critical notification popups. Toggle Light/Dark themes - Quickly switch between preferred light and dark themes. Terminal shell integration - Display command status, run recent commands, and more. Task output decorations - Highlights task success or failure exit codes. Git Commit action button - Configure your default Git Commit action.

Debug Step Into Target support - Allows you to step directly into functions when paused. JavaScript sourcemap toggling - Switch to debugging compiled rather than source code. Color theme tester - Use vscode.dev to preview color themes. VS Code Server preview - Run the same server used for Remote Development. If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Watch the release party: Listen in as the VS Code team discusses some of the new features.

You can find the recording of the event on our YouTube channel. Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Workbench 3 way merge editor In this release, we continued working on the 3-way merge editor. This feature can be enabled by setting git.mergeEditor to true and will be enabled by default in future releases.

The merge editor allows you to quickly resolve Git merge conflicts. When enabled, the merge editor can be opened by clicking on a conflicting file in the Source Control view. Checkboxes are available to accept and combine changes in Theirs or Yours : All language features are available in the merge editor (including diagnostics, breakpoints, and tests), so you get immediate feedback about any issues in the merged result.

The result can also be edited directly. Note how the checkbox updates as expected: When closing the merge editor or accepting the merge, a warning is shown if not all conflicts have been addressed. The merge editor supports word-level merging - as long as the changes don't intersect, both sides can be applied. If the insertion order matters, it can be swapped. At any time, the conflict can also be resolved manually. We would love to hear your feedback!

To share a merge conflict with us, use the command Merge Editor (Dev): Copy Contents of Inputs, Base and Result from JSON and paste the content in your GitHub issue. Command Center The Command Center has been polished and is now ready to be tried. Enable it via window.commandCenter setting. The Command Center replaces the normal title bar and lets you quickly search for files in your project. Click the main section to display the Quick Open dropdown with your recent files and a search box.

Theme: GitHub Theme The Command Center also has a button on the right to display the Quick Access options via '?'. On the left are Go Back and Go Forward buttons to navigate through your editor history. Settings editor modified indicator The Settings editor now shows when a setting has a language override. For context, language overrides always take precedence over non-language-specific overrides, so if the value of a setting doesn't seem to affect the behavior of the setting for a certain type of file, it could be that the setting has a language override.

The indicator text was changed to be more clear and concise. The short video below shows the new Modified elsewhere indicator. Hovering over the indicator reveals a hover that shows language overrides, when applicable. The video later shows the new default override indicator with the text Default value changed . Theme: Light Pink Do Not Disturb mode The new Do Not Disturb mode hides all non-error notification popups when enabled.

Progress notifications will be automatically shown in the Status bar. Hidden notifications are still available to view in the Notification center. You toggle Do Not Disturb mode by opening the Notification center (select the bell icon in the right of the Status bar) and clicking the slash bell icon. Do Not Disturb mode is indicated in the Status bar by the slash bell icon. Toggle between Light and Dark themes A new command allows you to toggle between your preferred light and dark themes, Preferences: Toggle between Light/Dark Themes .

When in a light theme, the command switches to a dark theme and vice versa. When in a high contrast theme, the command remains in high contrast and switches to the preferred high contrast theme of the opposite color theme. The preferred themes are defined by the settings: workbench.preferredDarkColorTheme workbench.preferredLightColorTheme workbench.preferredHighContrastColorTheme workbench.preferredHighContrastLightColorTheme Minimap context menu The VS Code minimap displays a high level outline of your source code file on the side of the editor.

You have been able to toggle the visibility of the minimap via the View: Toggle Minimap command or disable the minimap completely with the Editor > Minimap: Enabled ( editor.minimap.enabled ) setting. With this release, there is now a context menu to easily show or hide the minimap. You can also tune the appearance with the Size ( editor.minimap.size ), Scale ( editor.minimap.scale ), and Slider ( editor.minimap.showSlider ) settings.

If the minimap is hidden, you can still display the context menu by right-clicking the side gutter. Share menu The Copy vscode.dev Link command can be used from the File > Share submenu to quickly get a vscode.dev link for your open GitHub repository. The Share submenu is also available from the editor context menu. Terminal Shell integration Shell integration for PowerShell, bash, and zsh that has been in preview since the January release is now out of preview!

We're planning on enabling it by default in the 1.70 release. To enable the shell integration feature, check Terminal > Integrated > Shell Integration : Enabled in the Settings editor or set the value in your settings.json : "terminal.integrated.shellIntegration.enabled" : true Shell integration allows VS Code's terminal to understand more of what's going on inside the shell in order to enable more features. One of the goals with shell integration was for it to work with zero configuration required .

This was achieved by automatically "injecting" the shell integration script into the shell session via shell arguments and/or environment variables when the setting is enabled. There are some cases where this does not work such as in sub-shells or some complex shell setups, but we also have a manual install route for those more advanced cases. Below is a summary of the features shell integration currently provides: Command decorations and the overview ruler Shell integration has the ability to get the exit codes of the commands run within the terminal.

Using this information, decorations are added to the left of the line to indicate whether the command succeeded or failed. These decorations also show up in the overview ruler in the scroll bar, just like in the editor. The decorations can support contextual actions like rerunning the command: The command decorations can be configured with the following settings: terminal.integrated.shellIntegration.decorationIcon terminal.integrated.shellIntegration.decorationIconSuccess terminal.integrated.shellIntegration.decorationIconError Command navigation The commands detected by shell integration f

The rest of this page is on the live site.