Update release notes

release-notes/v1_55.md

@@ -78,6 +78,10 @@ You can now filter problems that do not contain specific text from the **Problem
 
 Last month we highlighted that there's a new [public repository](https://github.com/microsoft/vsmarketplace) for issues related to the Extension Marketplace. Now, VS Code's issue reporter supports creating issues in this repository.
 
+### Configure tree hover delay
+
+The hover delay for extension contributed tree views can now be configured with `workbench.hover.delay`.
+
 ### Emmet
 
 The `emmet.extensionsPath` setting now takes in only string arrays, and can be directly edited in the Settings editor.
@@ -252,6 +256,10 @@ There are two new menu locations, which appear in the UI as a **Copy As** submen
 
 ![Copy As submenu](images/1_55/copyas.png)
 
+### Docker compose language
+
+A new Docker compose language has been added. This won't have much user facing change; however, extension authors can now use this to target Docker compose files.
+
 ## Proposed extension APIs
 
 Every milestone comes with new proposed APIs and extension authors can try them out. As always, we want your feedback. This is what you have to do to try out a proposed API:
@@ -276,6 +284,10 @@ The proposed `triggerKind` property on `CodeActionContext` tracks why code actio
 
 Providers can use `triggerKind` to return different sets of results depending on how code actions are requested. For example, a refactoring code action provider that is triggered automatically may only return refactorings for the exact current selection in order to limit how often the code action lightbulb shows up. However when code actions are explicitly requested, the same provider may automatically expand the current selection to try to show all the refactorings that a user may be interested in at the current location.
 
+### PortAttributesProvider
+
+Any extension that starts processes that listen on ports and wants to have a stellar experience when used with a [VS Code remote extension](https://code.visualstudio.com/docs/remote/remote-overview) should consider providing feedback and adopting the new `PortsAttributesProvider` API. Since VS Code detects and automatically forwards ports when using one of the remote extensions, any extension that listens on ports will have those ports automatically forwarded. Often though, these ports are only important for the internal workings of the extension, and it isn't actually useful for the user to have these ports forwarded. This API can be used to set the behavior when when a ports is detected to preven unwanted auto-forwarding of ports that shouldn't be user facing.
+
 ## Language Server Protocol
 
 A draft version of the [diagnostic pull model specification](https://github.com/microsoft/vscode-languageserver-node/blob/master/protocol/src/common/proposed.diagnostics.md#L1) is now available for feedback.
@@ -328,6 +340,7 @@ There is a new topic describing how to install [VS Code on Raspberry Pi](https:/
 - [118210](https://github.com/microsoft/vscode/issues/118210): debug console shouldn't collapse messages when they have different source locations
 - [118557](https://github.com/microsoft/vscode/issues/118557): Strange behavior of files.exclude in workspace with nested folders
 - [118839](https://github.com/microsoft/vscode/issues/118839): My screen reader does not find information about a remote connection in the status bar
+- [119585](https://github.com/microsoft/vscode/issues/119585): All problems disappear when closing file
 
 ## Thank you
 

remote-release-notes/v1_55.md

@@ -15,6 +15,36 @@ Due to overlap with existing browser keybindings, we have changed the following
 * **Step Over** is now using `Alt + F10` instead of `F10` on all browsers.
 * **Step Into** is now using `Alt + F11` instead of `F11` on Windows browsers.
 
+### Detection of ports where the processes is root
+
+Port forwarding auto-detection now detects some ports where the process that is listening on a port is running as root. These ports will only be auto-detected if the command line for the process contains the port number.
+
+### Double click to name port
+
+Double clicking on a port in the Ports view will allow you to name the port.
+
+### Use a regex for `portsAttributes`
+
+The `remote.portsAttributes` setting can accept a regular expression as one of it's properties. This regular expression will be used to match against the command line of ports to forwarded. For example, if you don't know what port your application listens on, but you know that the command line will contain the string "/server.js" and you want to open a preview of your app when it runs you could add this setting:
+
+```json
+"remote.portsAttributes": {
+    ".+/server.js": {
+        "onAutoForward": "openPreview"
+    }
+}
+```
+
+### Configure default port dectection behavior
+
+The setting `remote.otherPortsAttributes` can be used to configure the behavior of any ports that aren't configured usint `remote.portsAttributes`. If, for example, you want all other ports that are detected to be silently (i.e., no notification or opening) forwarded then you can configure it with `remote.otherPortsAttributes`:
+
+```json
+"remote.otherPortsAttributes": {
+    "onAutoForward": "silent"
+}
+```
+
 ## Containers (version 0.166.x)
 
 ### Clone Repository in Container Volume improvements