prepare: v1.112.0

Author: connor4312

.github/prompts/rev.prompt.md

@@ -0,0 +1,15 @@
+---
+name: rev
+description: Update the version
+---
+
+<!-- Tip: Use /create-prompt in chat to generate content with agent assistance -->
+
+The user will give you a target revision version.
+
+0. Check out a new branch `rev/<version>`
+1. Review the changes since the last released version
+2. Update the CHANGELOG.md as necessary, creating a header for the current version, adding any new notes in there in the style of existing notes, and then adding a new "Unreleased" header
+3. Use the "ask questions" tool to confirm with the user that the notes are good or ask for their feedback on the generated notes
+4. Update the version in the package.json, then run `npm install` so the package-lock is updated to
+5. Commit everything as `prepare: v<version>`, create a PR, and set it to auto-merge

CHANGELOG.md

@@ -6,6 +6,12 @@ This changelog records changes to stable releases since 1.50.2. "TBA" changes he
 
 Nothing, yet
 
+## 1.112 (March 2026)
+
+- feat: support debugging integrated browser ([#2329](https://github.com/microsoft/vscode-js-debug/pull/2329))
+- fix: filter empty string args to prevent node from hanging ([#2328](https://github.com/microsoft/vscode-js-debug/issues/2328))
+- fix: debug session not terminating when browser closed from elevated VS ([#2327](https://github.com/microsoft/vscode-js-debug/issues/2327))
+
 ## 1.110 (February 2026)
 
 - feat: add `Symbol.for("debug.properties")` for custom property replacement in debugger ([vscode#102181](https://github.com/microsoft/vscode/issues/102181))

package-lock.json

@@ -1,7 +1,7 @@
 {
   "name": "js-debug",
   "displayName": "JavaScript Debugger",
-  "version": "1.110.0",
+  "version": "1.112.0",
   "publisher": "ms-vscode",
   "author": {
     "name": "Microsoft Corporation"