[pull] main from microsoft:main

.github/workflows/pr-darwin-test.yml

@@ -212,7 +212,7 @@ jobs:
         if: always()
 
       - name: Publish Crash Reports
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -223,7 +223,7 @@ jobs:
       # In order to properly symbolify above crash reports
       # (if any), we need the compiled native modules too
       - name: Publish Node Modules
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -232,7 +232,7 @@ jobs:
           if-no-files-found: ignore
 
       - name: Publish Log Files
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: always()
         continue-on-error: true
         with:

.github/workflows/pr-linux-test.yml

@@ -258,7 +258,7 @@ jobs:
         if: always()
 
       - name: Publish Crash Reports
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -269,7 +269,7 @@ jobs:
       # In order to properly symbolify above crash reports
       # (if any), we need the compiled native modules too
       - name: Publish Node Modules
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -278,7 +278,7 @@ jobs:
           if-no-files-found: ignore
 
       - name: Publish Log Files
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: always()
         continue-on-error: true
         with:

.github/workflows/pr-win32-test.yml

@@ -249,7 +249,7 @@ jobs:
         if: always()
 
       - name: Publish Crash Reports
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -260,7 +260,7 @@ jobs:
       # In order to properly symbolify above crash reports
       # (if any), we need the compiled native modules too
       - name: Publish Node Modules
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: failure()
         continue-on-error: true
         with:
@@ -269,7 +269,7 @@ jobs:
           if-no-files-found: ignore
 
       - name: Publish Log Files
-        uses: actions/upload-artifact@v6
+        uses: actions/upload-artifact@v7
         if: always()
         continue-on-error: true
         with:

.github/workflows/screenshot-test.yml

@@ -73,14 +73,14 @@ jobs:
           fi
 
       - name: Upload explorer artifact
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: component-explorer
           path: /tmp/explorer-artifact/
 
       - name: Upload screenshot report
         if: steps.compare.outcome == 'failure'
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: screenshot-diff
           path: |

extensions/CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing to Built-In Extensions
+
+This directory contains built-in extensions that ship with VS Code.
+
+## Basic Structure
+
+A typical TypeScript-based built-in extension has the following structure:
+
+- `package.json`: extension manifest.
+- `src/`: Main directory for TypeScript source code.
+- `tsconfig.json`: primary TypeScript config. This should inherit from `tsconfig.base.json`.
+- `esbuild.mts`: esbuild build script used for production builds.
+- `.vscodeignore`: Ignore file list. You can copy this from an existing extension.
+
+TypeScript-based extensions have the following output structure:
+
+- `out`: Output directory for development builds
+- `dist`: Output directory for production builds.
+
+
+## Enabling an Extension in the Browser
+
+By default extensions will only target desktop. To enable an extension in browsers as well:
+
+- Add a `"browser"` entry in `package.json` pointing to the browser bundle (for example `"./dist/browser/extension"`).
+- Add `tsconfig.browser.json` that typechecks only browser-safe sources.
+- Add an `esbuild.browser.mts` file. This should set `platform: 'browser'`.
+
+Make sure the browser build of the extension only uses browser-safe APIs. If an extension needs different behavior between desktop and web, you can create distinct entrypoints for each target:
+
+- `src/extension.ts`: Desktop entrypoint.
+- `src/extension.browser.ts`: Browser entrypoint. Make sure `esbuild.browser.mts` builds this and that `tsconfig.browser.json` targets it.