July 2024 (version 1.92)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. July 2024 (version 1.92) Update 1.92.1 : The update addresses these issues . Update 1.92.2 : The update addresses these issues . Downloads for 1.92.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the July 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include: Default browser - Configure which browser to use for opening links in VS Code.
Revert PRs - Easily create a revert PR for a merged PR. Extension updates - More easily configure auto updating of extensions. Override profiles - Override an existing profile with the Profiles Editor. Paste files in CSS - Quickly add CSS file references with paste or drag and drop. Move Panel to top - Position the Panel section at the top of the workbench. Copilot uses GPT-4o - GitHub Copilot Chat upgraded to OpenAI's GPT-4o.
If you'd like to read these release notes online, go to Updates on code.visualstudio.com . 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. Accessibility Improved debugging experience Accessibility help dialogs We added accessibility help dialogs for the Run and Debug view and Debug Console. You get a hint about opening the accessible help dialog when either view is focused.
Configure this hint via the setting accessibility.verbosity.debug . Debug Console Accessible View Run the command Open Accessible View ( ⌥F2 (Windows Alt+F2 , Linux Shift+Alt+F2 ) ) to inspect Debug Console content character by character, line by line. The setting debug.autoExpandLazyVariables is now enabled when in Screen Reader Optimized Mode , for ready access to variable values. When an expression is evaluated in the Debug Console, its value is now announced to screen reader users.
Dynamic watch variable announcement When debugging with a screen reader enabled, you now hear when watch variable values change. Configure this with accessibility.debugWatchVariableAnnouncements . Configure keybindings action In the previous milestone, we introduced an action to configure unassigned keybindings in the accessibility help dialog. We've now added the Configure Assigned Keybindings command ( ⌥A (Windows, Linux Alt+A ) ) to complement this action.
Workbench Move Panel to top You can now move the Panel to the top of the workbench, above the editor area. By default, the Panel is placed at the bottom and includes views, such as the terminal, Output panel, and Debug Console. This enhancement complements the existing options of positioning the panel to the left, right, and bottom. Profiles Editor preview In this milestone, we continued to improve the Profiles Editor by making it more user-friendly and by having a look and feel that's consistent with the Settings Editor.
The Profiles Editor is available as an experimental feature behind the workbench.experimental.enableNewProfilesUI setting. Once enabled, you can access the Profiles Editor from the Settings gear icon in the bottom left corner of the window. Override existing profile You can now override an existing profile, including the default profile, by creating a new profile with the same name. Improved extension update experience We made several improvements to the extension update experience to give you more control over updating extensions and make it easier to manage auto updating of extensions.
Auto updating all extensions We have changed the global extension auto update action in the Extension view title area to Enable Auto Update for All Extensions and Disable Auto Update for All Extensions actions. With these actions, you can enable or disable auto update for all extensions at once. Auto updating individual extensions We improved the individual extension auto update experience by always showing the action to enable or disable auto update for the extension.
This makes it easier to manage auto updating of extensions. Disable auto update for extensions installed via VSIX When you install an extension via VSIX, auto update for that extension is disabled by default. This enables you to work with the version of the extension you have installed, without it being updated automatically. More control over updating extensions User consent is now required when you update an installed extension version that has no executable code to a version that has executable code.
This gives you control to review such updates before they are applied. The following video demonstrates the experience when updating an extension with no code to a version with code. Selecting the Review button opens the extension change log or the extension repository in the browser. You can review the changes and then decide if you want to update the extension. Settings Editor jump issue fixed The Settings Editor used to jump after modifying a setting and changed focus to another one.
And this jump was worse the more one scrolled before modifying a setting. We changed the way the Settings Editor re-renders settings after modification, and the Settings Editor no longer jumps after modifying a setting. Theme: Light Pink (preview on vscode.dev ) URL handling for settings VS Code can now handle "settings" URLs of the format vscode://settings/setting.name ( vscode-insiders://settings/setting.name for Insiders, and code-oss for the OSS version) and will open the Settings Editor to the specified setting.
If no setting is given, then the Settings Editor is still opened. When an anchor tag with a settings URL is used in the release notes, and the release notes are open in VS Code, then we do special handling and rendering, as described in the previous codesetting feature. Configure the browser to open links A new setting workbench.externalBrowser enables you to configure which browser to use for opening links. By default, the operating system standard browser is used.
You can configure this setting on a per-workspace level and is also Settings Sync enabled. Specify the full path to the browser executable as the settings value. Alternatively, to ensure correct functioning across devices, you can also use browser aliases, such as edge , chrome , or firefox . Disable auto file open on drag and drop Previously, dragging and dropping a file into the explorer would also automatically open it in the editor.
In some cases, this might be undesirable. A new setting explorer.autoOpenDroppedFile enables you to toggle this behavior. By default, the file continues to be opened when dragged and dropped, but when set to false , this behavior is disabled. Editor Lightbulb control improvements At times, the lightbulb control might block code in the editor. To address this, we introduced an improved heuristic for the lightbulb control, which displays the lightbulb in the gutter when there is no space, instead of blocking code in the editor.
You can toggle the lightbulb control in the editor with the editor.lightbulb.enabled setting. Diff Editor More compact diffs in Chat We iterated on the diff editor layout in the Chat view/inline Chat and made it more compact. Before : After : Source Control Incoming/Outgoing changes graph This milestone, we are enabling the visualization of the incoming and outgoing changes using a graph. The graph contains the current branch, the current branch's upstream branch, and an optional base branch.
The root of the graph is the common ancestor of these branches. We have made several improvements to the history item hover: Enabled multi-select to see changes across multiple history items that belong to the same branch. Added options to the ... menu to filter history items from the remote/base branches. Added actions to fetch, pull, and push history items. Give it a try and let us know what you think! You can disable the graph visualization of incoming
The rest of this page is on the live site.