Merge branch 'vnext' of https://github.com/microsoft/vscode-docs into vnext

Author: ntrogh

release-notes/v1_96.md

@@ -40,6 +40,8 @@ Welcome to the November 2024 release of Visual Studio Code. There are many updat
 
 ### Copilot Edits
 
+Last milestone we introduced [Copilot Edits](https://code.visualstudio.com/docs/copilot/copilot-edits) (currently in preview), which allows you to quickly edit multiple files at once using natural language. Since then, we've continued to iterate on the experience. You can try out Copilot Edits by opening the Copilot menu in the Command Center, and then selecting Open Copilot Edits, or triggering `kb(workbench.action.chat.openEditSession)`.
+
 #### Progress and editor controls
 
 Copilot Edits can make multiple changes across different files. You can now more clearly see its progress as edits stream in. And with the editor overlay controls, you can easily cycle through all changes and accept or discard them.
@@ -530,6 +532,12 @@ Designed to integrate seamlessly with your preferred environment managers via va
 * Testing Rewrite now leverages FIFO instead of UDS for interprocess communication allowing users to harness pytest plugins like `pytest_socket` in their own testing design.
 * **Rewrite Nearing Default Status:** This release addresses [the final known issue](https://github.com/microsoft/vscode-python/issues/23279) in the testing rewrite, and unless further issues arrive, the rewrite experiment will be turned off and the rewrite set to default in early 2025.
 
+#### Python REPL enhancements
+
+* Leave focus on editor after smart-send to Native REPL
+* Improved handling after reload for Native REPL
+* Fix indentation error issues when Python 3.13 in VS Code terminal
+
 #### Pylance "full" language server mode
 
 The `python.analysis.languageServerMode` setting now also supports `full` mode, enabling you to take advantage of the complete range of Pylance's functionality and the most comprehensive IntelliSense experience. It's worth noting that this comes at the cost of lower performance, as it can cause Pylance to be resource-intensive, particularly in large codebases.