**Update 1.74.1**: The update addresses these [issues](https://github.com/microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22November+2022+Recovery+1%22+is%3Aclosed).
**Update 1.74.2**: The update addresses these [issues](https://github.com/microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22November+2022+Recovery+2%22+is%3Aclosed).
Welcome to the November 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:
>If you'd like to read these release notes online, go to [Updates](https://code.visualstudio.com/updates) on [code.visualstudio.com](https://code.visualstudio.com).
**Insiders:** Want to try new features as soon as possible? You can download the nightly [Insiders](https://code.visualstudio.com/insiders) build and try the latest updates as soon as they are available.
There are now [audio cues](https://code.visualstudio.com/docs/editor/accessibility#_audio-cues) for when notebook cells finish running. The cue is different to indicate whether the cell ran successfully or failed.
In a diff editor, when **Go to Next Difference** is triggered, a specific audio cue will play to indicate whether the cursor is on an inserted or deleted line.
### Keyboard-navigable Settings editor indicators, hovers, and links
The indicators, hovers, and links in the Settings editor are now navigable by keyboard. The styling of some of the links have also been adjusted for better consistency across the Settings editor.
Settings editor indicator hovers now behave much better when it comes to tabstops and maintaining keyboard focus. This improved behavior is still experimental, and is currently only enabled for the Settings editor indicator hovers, rather than for all hovers across VS Code.
The highly upvoted [issue #87956](https://github.com/microsoft/vscode/issues/87956) ("Allow to set explorer.autoReveal per specific folder") has been fixed by the introduction of a new setting `explorer.autoRevealExclude`. This setting lets you configure which files get autorevealed in the Explorer if the autorevealing is enabled (`explorer.autoReveal`, default `true`). The `autoRevealExclude` setting uses [glob patterns](https://code.visualstudio.com/docs/editor/codebasics#_advanced-search-options) for excluding files and similar to `files.exclude`, also supports sibling matching via when clauses.
Similar to how you were able to hide view containers by right-clicking the view container, you can now hide the badge on the container (displayed in the Activity bar, Panel, and Secondary Side bar). Badges often display a number, icon, or progress indicator for a specific view container, for example, the number of pending changes for the Source Control view.
### Merge Editor
This release ships some improvements and bug-fixes for the merge editor. Highlights include:
* Undo/Redo now tracks the handled state of conflicts.
* **Ignore** actions in the input views can be used to accept the base version instead of the **Mark as handled** action in the result view.
* Changes that are equal on both sides are now automatically resolved.
You can now install an extension that is located on a local disk drive by using **Developer: Install Extension from Location...** command. The command will open the platform folder dialog to select the location of the extension's `.vsix` file.
A setting called `editor.wordBreak` can now be used to avoid inserting wrapping points after [CJK characters](https://en.wikipedia.org/wiki/CJK_characters). When configured with `keepAll`, the wrapping algorithms will try to keep text after CJK characters on the same line. This setting doesn't have any effect on characters from other scripts.
Some newer fonts, which support [OpenType](https://learn.microsoft.com/typography/opentype) font variations, support tuning certain axes, like the font weight axis, to achieve font weights that are not configurable via the `font-weight` CSS property. In CSS, this is achieved with the `font-variation-settings` property. If you use such a font, you can now configure `editor.fontVariations` to `true`, which will result in VS Code using the `"wght"` display axis for setting the font weight. If your font supports other axes, it is also possible to configure them directly, for example by setting `"editor.fontVariations": "'ital' 0.5"`.
There is a new setting called `editor.indentSize` that allows to dissociate the indent size (the number of spaces that make up an indent) from the tab size (the number of spaces that are used to render a Tab character). This is useful when dealing with files that use mixed tabs and spaces indentations and can be exercised only when using manual indentation configuration.
### Command to partially accept inline completions
The command **Accept Next Word Of Inline Suggestion** (`editor.action.inlineSuggest.acceptNextWord`) can be used to accept the next word/non-word segment of the current inline suggestion. Currently, it can only accept parts of the first line of an inline suggestion. The command is still under development and we are exploring keyboard shortcuts along with alternative splitting rules for future releases.
VS Code uses `git.exe` for executing all Git operations. Starting with Git [2.35.2](https://github.blog/2022-04-18-highlights-from-git-2-36/#stricter-repository-ownership-checks), users are prevented from running Git operations in a repository that is in a folder owned by a user other than the current user, as the repository is deemed to be potentially unsafe.
Starting with this release, if you try to open such a potentially unsafe repository, VS Code will show a welcome view in the Source Control view as well as an error notification. Both the welcome view, and the notification expose the **Manage Unsafe Repositories** command that lets you review the list of potentially unsafe repositories, mark them as safe, and open them. The **Manage Unsafe Repositories** command is also available in the Command Palette. Marking a repository as safe will add the repository location to the `safe.directory` [git configuration](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory).
After executing a Git operation, a set of `git` commands (for example, `git status`) are executed to update the data model before the Source Control view is updated. There are scenarios in which running these commands can take several seconds to complete (for example, when working with large monorepos), resulting in a delay before the Source Control view is refreshed.
This milestone we have made changes so that the Source Control view is optimistically updated for some of the Git operations (stage, unstage, discard changes, and commit) before `git status` completes, resulting in a snappier Source Control view.
When the **Commit** action button is executing a secondary commit command (for example, **Commit & Sync**), the button label now correctly reflects the command being executed. The **Commit** button also shows an animation indicating progress.
Terminal Quick Fixes are now presented in a Code Action control to align with the experience in the editor.
### Task actions in the terminal dropdown
The **Run Task** and **Configure Tasks** commands appear in the terminal dropdown for increased discoverability and ease of access.
[Remote Tunnels](https://code.visualstudio.com/docs/remote/tunnels) is now available as a preview feature on VS Code Stable. Remote tunnels allow you to securely access your machine with VS Code from any device, anywhere. To enable remote tunnel access, you can **either**:
Once tunnel access is turned on, you can connect to the machine from any device using [vscode.dev](https://vscode.dev), or using the [Remote - Tunnels](https://marketplace.visualstudio.com/items?itemName=ms-vscode.remote-server) extension from within VS Code Desktop.
To find out more, check out our [blog post announcing the feature](https://code.visualstudio.com/blogs/2022/12/07/remote-even-better) or the [Remote Tunnels](https://code.visualstudio.com/docs/remote/tunnels) documentation.
<videosrc="images/1_74/tunnels-turn-on.mp4"placeholder="images/1_74/tunnels-turn-on.mp4"autoplayloopcontrolsmutedtitle="Video showing usage of 'Turn on Remote Tunnel Access'">
_Theme: [Codesong](https://marketplace.visualstudio.com/items?itemName=connor4312.codesong) (preview on [vscode.dev](https://vscode.dev/editor/theme/connor4312.codesong))_
> **Note:** If you were using the standalone `code-server` CLI, you should now use the VS Code CLI (via the latest VS Code Desktop or the standalone download mentioned above) instead.
## Debugging
### JavaScript debugging
**Support for console.profile**
The JavaScript debugger now supports [console.profile](https://developer.mozilla.org/docs/Web/API/console/profile). When running under the debugger, a CPU profile will be collected for code between `console.profile()` and `console.profileEnd()`.
The resulting `.cpuprofile` file will be saved in your workspace folder, and can be opened and viewed using VS Code's built-in [profile viewer](https://code.visualstudio.com/docs/nodejs/profiling).
Sometimes, especially in monorepo setups, source code might be compiled once and then recompiled or bundled again. In many cases, this would result in sourcemaps of the resulting bundle referencing the compiled files created in the first step.
The [serverReadyAction](https://code.visualstudio.com/docs/editor/debugging#_automatically-open-a-uri-when-debugging-a-server-program) `launch.json` feature enables users to start a debug session that starts a web server, then once the server starts, automatically start debugging a browser navigated to that server's URL. There is a new property, `killOnServerStop` that when set to `true`, will cause the new browser debug session to be automatically stopped when the server debug session stops.
### Exception breakpoints shown for the focused debug session
Managing exception breakpoints when running two different types of debug sessions did not work well previously. Now, when a debug session is focused in the **Call Stack** view, the correct set of breakpoints for that session's debug type will be shown.
## Comments
### comments.visible
The new setting `comments.visible` can be used to turn off editor commenting (the Comments bar and the in-editor Comments Peek view). The command **Comments: Toggle Editor Commenting** can still be used to toggle editor commenting on and off during a session. Selecting a comment in the **Comments** view will always toggle commenting on.
### Comments view badge
The **Comments** view shows a badge for the count of unresolved comments.
Previously, problem matchers needed to know exactly where to look for the problematic files, via the `fileLocation` property. The supported methods were `absolute`, `relative`, or `autoDetect` (check for relative paths first, then look for absolute paths in case of failure).
However, in workspaces that use scripts residing in nested subdirectories, it was difficult to set up tasks as different scripts seldom report file paths in a unified manner (for example, relative to the workspace's base directory).
To help with this problem, there is a new file location method, named `search`. With this method, a recursive file system search is run to locate any captured path.
The example below shows how to set up the `search` file location method (although, all parameters are optional):
```jsonc
"problemMatcher": {
// ...
"fileLocation": [
"search",
{
"include": [ // Optional; defaults to ["${workspaceFolder}"]
"${workspaceFolder}/src",
"${workspaceFolder}/extensions"
],
"exclude": [ // Optional
"${workspaceFolder}/extensions/node_modules"
]
}
],
// ...
}
```
**Note** that users should be wary of causing **time consuming file system searches** (for example, looking inside `node_modules` directories) and set the `exclude` property appropriately.
## Languages
### TypeScript 4.9
VS Code now ships with TypeScript 4.9. This major update brings new TypeScript language features such as the [`satisfies` operator](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/#satisfies) and [auto accessors](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/#auto-accessors-in-classes). On the tooling side, we've made improvements to [file watching](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/#file-watching-changes) and made a number of other fixes and improvements.
Check out the [TypeScript 4.9 announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/) for more about this update.
JavaScript and TypeScript now support running **Go to Definition** on the `return` keyword to quickly jump to the top of the function being returned from. This is helpful when dealing with long, complicated, or highly nested functions. You can use the **Go to Definition** command/keybinding for this (`kb(editor.action.revealDefinition)`) or simply `Cmd/Alt + Click` on the `return` keyword.
There is a new notebook kernel picker that shows the most recently used kernels at the top of the picker. This is an opt-in experiment that can be enabled by setting the `notebook.kernelPicker.type` setting to `mru`.
Kernels that are not used will be moved into a secondary picker **Select Another Kernel...**. This picker will group all kernels by their source (for example: Jupyter Kernel, Python Environment, etc.) when you have latest [Jupyter extension](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) installed.
We would love to hear your feedback and you can create issues in the [VS Code repository](https://github.com/microsoft/vscode/issues).
## VS Code for the Web
### Source control
VS Code for the Web now supports the following settings when editing GitHub and Azure Repos repositories:
*`"git.branchRandomName.enabled"` - Generate random branch name when creating branches in VS Code for the Web.
*`"git.branchRandomName.dictionary"` - Specify word dictionaries for generating random branch names when creating branches in VS Code for the Web.
*`"git.closeDiffOnOperation"` - Close diff editors after performing source control operations like committing, staging, unstaging changes.
Additionally, VS Code for the Web displays a lock icon in the Status bar and the branch picker for protected branches, aligning with the experience on VS Code Desktop.
Finally, you can now use the source control action button in VS Code for the Web to commit and push your changes directly to the repository remote:
If you wish to validate your changes before committing, you can also use the secondary **Continue Working On...** action in the action button dropdown to take your working changes to another development environment.
When you are in a GitHub or Azure Repos repository, there are now convenient one step commands available in the Command Palette to take your working changes with you to a specific development environment:
The "Just My Code" debug feature allows you to determine whether the debugger will step through code from Python libraries, or will only step through your source code. This has been enabled by default when debugging a notebook cell, but you can set `"jupyter.debugJustMyCode": false` to disable it and let you step through library code. For the best experience, upgrade debugpy in your environment to `>=1.6.3`. Previously, the `debugJustMyCode` setting was only respected when debugging in the Interactive Window and now it is available for notebook editors as well.
The **Restart** command in the debug toolbar restarts the current debug session. Previously, this threw an error in notebook debug sessions, but now it is supported. Unfortunately, it can't be properly supported in the Interactive Window.
This feature is especially useful in a workflow where you debug, edit the cell, then restart the debug session to debug the cell again with your edits applied.
### Remote Development extensions
The [Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack), allow you to use a container, remote machine, or the [Windows Subsystem for Linux](https://learn.microsoft.com/windows/wsl) (WSL) as a full-featured development environment. Highlights of this release include:
* Dev Container GPU support
* Dev Container Cygwin / Git Bash sockets forwarding
* [Remote - Tunnels](https://marketplace.visualstudio.com/items?itemName=ms-vscode.remote-server) extension - Connect to a remote machine without requiring SSH.
You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_74.md).
There has been more progress on the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, which allows you to work on, create, and manage pull requests and issues. Highlights include:
* vscode.dev links for PRs can be copied from the pull request overview.
* The command **Go To Next Diff in Pull Request** navigates to the next diff in a checked out PR across files.
Check out the [changelog for the 0.56.0](https://github.com/microsoft/vscode-pull-request-github/blob/main/CHANGELOG.md#0560) release of the extension to see the other highlights.
## Preview features
### Profiles
We have been working the last couple of months to support **Profiles** in VS Code, which is one of the most popular asks from the community. This feature is available for preview via the `workbench.experimental.settingsProfiles.enabled` setting. Try it out and give us your feedback by creating issues in the [vscode repository](https://github.com/microsoft/vscode/issues) or commenting in [issue #116740](https://github.com/microsoft/vscode/issues/116740).
You can now share a profile by exporting it to GitHub as a gist. VS Code will create a secret gist using your GitHub account and provides you a link to share it with others. When you open that link, VS Code will ask you to install the shared profile. During exporting or importing a profile, VS Code will show a preview so that you can review and choose data to export or import respectively.
Starting mid-November, all VS Code extensions uploaded to the [Visual Studio Marketplace](https://marketplace.visualstudio.com/vscode) are signed by the VS Marketplace - this process is called repository signing. On every extension install and update, VS Code verifies the extension package signature. With signing and signature verification, we can guarantee extension package integrity and authenticity.
Signature verification is currently only done in VS Code Insiders. If you notice any issues, you can let us know by creating an issue in the [vscode repository](https://github.com/microsoft/vscode/issues) and you can opt out of signature verification by setting `extensions.verifySignature` to `false`. We are working on enabling signature verification in VS Code Stable in the coming months.
Apart from repository signing, we are also starting work on [extension publisher signing](https://github.com/microsoft/vscode-discussions/discussions/137).
### Python execution in the Web
We added debugging support to the [Experimental - Python for the Web](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-python-web-wasm) extension. The debugger supports the following features:
* Setting breakpoints
* Stepping into and out of functions
* Debug across modules
* Evaluate variables in the debug console
* Debug the program in the Integrated Terminal
The screenshot below shows debugging a `Hello World` program
**Note** that using the extension still requires you to add the following query parameter to the browser URL `?vscode-coi=`.
## Extension authoring
### Implicit activation events for declared extension contributions
This milestone we removed the requirement to explicitly list activation events if your extension declares certain extension contributions in its `package.json`.
Previously, if an extension declared that it contributed a command `mycommand` in its `package.json` file, it also needed to list the corresponding `onCommand:mycommand` activation event in the `activationEvents` field of `package.json` for the command to successfully execute. This was tedious and error-prone and could lead to large `package.json` files.
VS Code will now automatically populate activation events for the following extension contribution points:
| Contribution point | Inferred activation event |
| --- | --- |
| `commands` | `onCommand` |
| `authentication` | `onAuthenticationRequest` |
| `languages` | `onLanguage` |
| `customEditors` | `onCustomEditor` |
| `views` | `onView` |
Extension authors can now safely remove these inferred activation events from your extensions. If you do so, update your VS Code engine requirement to ensure that your extension is not treated as compatible with earlier versions of VS Code:
```json
"engines": {
"vscode": "^1.74.0"
},
```
### Log output channel
This milestone we finalized the [LogOutputChannel](https://github.com/microsoft/vscode/blob/930fd0e469a43fd923cd732c178e3cc9e878b58d/src/vscode-dts/vscode.d.ts#L6474) API. You can now use this API to create a log output channel that will be used to log messages from your extension.
We also finalized the [logLevel](https://github.com/microsoft/vscode/blob/930fd0e469a43fd923cd732c178e3cc9e878b58d/src/vscode-dts/vscode.d.ts#L9464) property and the [onDidChangeLogLevel](https://github.com/microsoft/vscode/blob/930fd0e469a43fd923cd732c178e3cc9e878b58d/src/vscode-dts/vscode.d.ts#L9469) event in the `env` namespace to indicate the current log level of the application and fire an event when the log level changes for the application.
Following up on [our work last iteration](https://code.visualstudio.com/updates/v1_73#_consistent-origin-for-webviews-and-webview-views), all webviews in VS Code now try to maintain custom origins. With 1.74, this also extends to the webviews used by custom editors.
This improves performance by allowing webview content to be cached in more cases. See the [previous release notes](https://code.visualstudio.com/updates/v1_73#_consistent-origin-for-webviews-and-webview-views) for more details and things to be aware of as an extension author.
Extensions can now use `<video>` tags in their READMEs. Videos are supported on both the VS Code Marketplace and on Extensions view pages in VS Code. Compared to `.gif`s, video files are higher quality and often smaller too. You can even include audio!
Keep in mind that [only specific video and audio formats](https://code.visualstudio.com/api/extension-guides/webview#_supported-media-formats) are supported in VS Code itself. At present, you must also use a full path to the `<video>``src` and `poster` instead of a relative path.
### Renaming of vsce to @vscode/vsce
The [vsce](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#vsce) tool, VS Code's extension manager, has been renamed to [@vscode/vsce](https://www.npmjs.com/package/@vscode/vsce). This is a breaking change for anyone using the tool as a library. The CLI tool is still called `vsce` and can be installed via `npm install -g @vscode/vsce`.
## Debug Adapter Protocol
Several clarifications and a new property were added to the [Debug Adapter Protocol](https://microsoft.github.io/debug-adapter-protocol).
* The `DataBreakpointInfo` request has a new optional `frameId` property. Clients can use this flag to specify which stack frame contains a `name` variable.
* End-of-file behavior is now specified for the `readMemory` request.
## Engineering
### Name mangling of properties and method
Our product build now mangles names of properties and methods. This reduced the size of our main bundles by ~13% (-1.5 MB) and reduces code loading times by ~5%.
### GitHub & Microsoft Authentication extensions bundle size improvements
The bundle sizes for these two extensions were larger than we wanted them to be, given what they provided and how critical they are for startup in many cases (such as vscode.dev). This milestone, we focused on decreasing the size of these extensions and here are the results:
* No longer depending (and bundling) node modules that provided functionality that is readily available in Node.js and the web (for example, removing `uuid` in favor of [Crypto.randomUUID()](https://developer.mozilla.org/docs/Web/API/Crypto/randomUUID)).
* Only using `node-fetch` in Node.js, instead of using it for both Node.js and the web.
* Adopting the newest version of `@vscode/extension-telemetry`, whose size decreased considerably.
You can learn about our progress toward enabling Electron's [sandbox](https://www.electronjs.org/docs/tutorial/sandbox) in the recent ["Migrating VS Code to Process Sandboxing"](https://code.visualstudio.com/blogs/2022/11/28/vscode-sandbox) blog post. This detailed article presents the technology timeline and describes the incremental changes made to support VS Code sandboxing.
If you want to try out VS Code sandbox mode, you can set `"window.experimental.useSandbox": true` in settings. Hopefully you should not notice any functional differences, but if you find issues, please report them back to us.
### Window Controls Overlay re-enabled by default on Windows
The [Window Controls Overlay](https://wicg.github.io/window-controls-overlay) (WCO) has been re-enabled by default. It was previously enabled in August, but then disabled again, because it was [rendering on the wrong side](https://github.com/microsoft/vscode/issues/159813) for users using right-to-left system languages, covering up the **File** and **Edit** menu items.
The main issue was that VS Code wasn't passing the application locale to Electron, so Electron used the system locale to determine where to place the WCO. However, VS Code relied on Electron's `app.getLocale()` API to obtain the system language and determine what language pack to recommend, and passing in the application locale to Electron resulted in `app.getLocale()` returning that same locale instead of the system language.
To fix the issue, we added a new `app.getPreferredSystemLanguages()` API to Electron so that even after passing the locale to Electron, we can still get the system language to use for VS Code's language pack recommender, while keeping the WCO on the right side.
### Built-in extensions now use the new l10n API instead of vscode-nls
Last month we stabilized the new [Localization (l10n)](https://code.visualstudio.com/api/references/vscode-api#l10n) API. This month, we have adopted that API in every extension found in the [Microsoft/vscode](https://github.com/microsoft/vscode/tree/main/extensions) repository. We still need to move language servers over to using `@vscode/l10n` instead of `vscode-nls` as well as some other extensions owned by the team (JS Debug, Python, Jupyter Notebooks, etc.) but we are moving in the right direction to a single localization story for all of our extensions.
* [@Albert-cord](https://github.com/Albert-cord): feat: Add wordBreak editorOption and use it to lineBreakComputer function [PR #156242](https://github.com/microsoft/vscode/pull/156242)
* [@andschwa (Andy Jordan)](https://github.com/andschwa): Support shell integration in Windows PowerShell [PR #167023](https://github.com/microsoft/vscode/pull/167023)
* [@babakks (Babak K. Shandiz)](https://github.com/babakks)
* 🐛 Fix repeated CWD entries when creating new terminal in multi-root workspace [PR #153204](https://github.com/microsoft/vscode/pull/153204)
* 🎁 Add `killOnServerStop` to debug configuration [PR #163779](https://github.com/microsoft/vscode/pull/163779)
* 🎁 Add `search` to file location methods in tasks [PR #165156](https://github.com/microsoft/vscode/pull/165156)
* 💄 Include file system path in debug mode's URI/link hovers [PR #165709](https://github.com/microsoft/vscode/pull/165709)
* 🔨 Add "Focus Breadcrumb" to command palette [PR #166461](https://github.com/microsoft/vscode/pull/166461)
* [@CGNonofr (Loïc Mangeonjean)](https://github.com/CGNonofr): Standalone configuration: use resource and language [PR #146522](https://github.com/microsoft/vscode/pull/146522)
* [@chengluyu (Luyu Cheng)](https://github.com/chengluyu): Support variable fonts (#153291) [PR #153968](https://github.com/microsoft/vscode/pull/153968)
* [@cmarincia (Catalin Marincia)](https://github.com/cmarincia): Add list of strings option to editor.fontFamily [PR #164289](https://github.com/microsoft/vscode/pull/164289)
* [@ecstrema (Rémi Marche)](https://github.com/ecstrema): Editor state change, break after match [PR #166283](https://github.com/microsoft/vscode/pull/166283)
* [@felixlheureux (Felix L'Heureux)](https://github.com/felixlheureux): Reset value to an empty string when undefined or null [PR #165721](https://github.com/microsoft/vscode/pull/165721)
* [@g1eny0ung (Yue Yang)](https://github.com/g1eny0ung): fix: text overlay in replace input [PR #162036](https://github.com/microsoft/vscode/pull/162036)
* Markdown lang preview settings description [PR #165109](https://github.com/microsoft/vscode/pull/165109)
* adds to `files.exclude` desc re: `explorer.excludeGitIgnore` [PR #165111](https://github.com/microsoft/vscode/pull/165111)
* [@jasonwilliams (Jason Williams)](https://github.com/jasonwilliams): fix #154064 which was running the wrong taskgroups [PR #164983](https://github.com/microsoft/vscode/pull/164983)
* [@JayBazuzi (Jay Bazuzi)](https://github.com/JayBazuzi): Change error message when launching a second admin instance [PR #166146](https://github.com/microsoft/vscode/pull/166146)
* [@Mingpan](https://github.com/Mingpan): Fix arrows in side-by-side diff view [PR #165423](https://github.com/microsoft/vscode/pull/165423)
* [@miyaokamarina (Marina Miyaoka)](https://github.com/miyaokamarina): Do not preprocess Unicode newlines in Markdown preview [PR #166026](https://github.com/microsoft/vscode/pull/166026)
* Use CSS variables over registerThemingParticipant - minimap viewparts [PR #165465](https://github.com/microsoft/vscode/pull/165465)
* Use CSS variables over registerThemingParticipant - rulers viewparts [PR #165466](https://github.com/microsoft/vscode/pull/165466)
* [@nisargjhaveri (Nisarg Jhaveri)](https://github.com/nisargjhaveri): Allow different exception breakpoints from multiple debuggers to be shown at once [PR #158355](https://github.com/microsoft/vscode/pull/158355)
* [@Okeanos (Nikolas Grottendieck)](https://github.com/Okeanos): improve Git Bash integration on Windows (#151105) [PR #165428](https://github.com/microsoft/vscode/pull/165428)
* [@sandersn (Nathan Shively-Sanders)](https://github.com/sandersn): Copy webServer from Typescript to VS Code [PR #165771](https://github.com/microsoft/vscode/pull/165771)
* [@SethFalco (Seth Falco)](https://github.com/SethFalco): feat: add setting for multi cursor limit [PR #149703](https://github.com/microsoft/vscode/pull/149703)
* [@SphinxKnight (SphinxKnight)](https://github.com/SphinxKnight): Nit: fix Tip blocks case [PR #165223](https://github.com/microsoft/vscode/pull/165223)
* [@ssigwart (Stephen Sigwart)](https://github.com/ssigwart): Fix unwanted extra spaces when pasting code with JSDoc [PR #136579](https://github.com/microsoft/vscode/pull/136579)
* move css variables for diffEditor [PR #166467](https://github.com/microsoft/vscode/pull/166467)
* [@yiliang114 (易良)](https://github.com/yiliang114): Only use string of the `remote/web/package.json``browser` field [PR #165163](https://github.com/microsoft/vscode/pull/165163)
* [@zeroimpl (Daniel Fiori)](https://github.com/zeroimpl): Separate tab size and indent size [PR #155450](https://github.com/microsoft/vscode/pull/155450)
* [@zhuowei](https://github.com/zhuowei): webview: ignore Ctrl+W and Ctrl+N in webview for PWA [PR #164981](https://github.com/microsoft/vscode/pull/164981)
Contributions to `vscode-css-languageservice`:
* [@babakks (Babak K. Shandiz)](https://github.com/babakks): ✋ Ignore missing standard properties in contexts with vendor-specific pseudo-elements [PR #303](https://github.com/microsoft/vscode-css-languageservice/pull/303)
* [@MariaSolOs (Maria José Solano)](https://github.com/MariaSolOs): Check for -- when disabling rules [PR #1506](https://github.com/microsoft/vscode-eslint/pull/1506)
* [@uhyo (uhyo)](https://github.com/uhyo): Add Experimental support of Flat Config [PR #1522](https://github.com/microsoft/vscode-eslint/pull/1522)
Contributions to `vscode-js-debug`:
* [@xai (Olaf Lessenich)](https://github.com/xai): fix: use platform preferred case in launcher [PR #1449](https://github.com/microsoft/vscode-js-debug/pull/1449)
* [@joshuaobrien (Joshua O'Brien)](https://github.com/joshuaobrien): Narrow types in TimelineEvent so that it may be treated as a tagged union [PR #4160](https://github.com/microsoft/vscode-pull-request-github/pull/4160)
* [@WardenGnaw (Andrew Wang)](https://github.com/WardenGnaw): Move EvaluateArguments context variables to end of enums [PR #346](https://github.com/microsoft/debug-adapter-protocol/pull/346)
Contributions to `devcontainers/cli`:
* [@amurzeau (Alexis Murzeau)](https://github.com/amurzeau): Handle Cygwin / Git Bash sockets forwarding on Windows [PR #82](https://github.com/devcontainers/cli/pull/82)
