Docs

vadimcn · Feb 17, 2025 · e5aef55 · e5aef55
1 parent b528bd1
commit e5aef55
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,14 @@
 # Release Notes
 
+# 1.11.4
+
+### Fixed
+- #1044: VS Code doesn't clear the extension folder after upgrading or uninstalling
+- #1228: SourceMaps stopped working for bazel-built processes on version 1.11.2 and 1.11.3
+
+### Changed
+- Updated bundled LLDB to v19.1.0
+
 # 1.11.3
 
 ### Fixed

diff --git a/MANUAL.md b/MANUAL.md
@@ -708,7 +708,7 @@ for use in CodeLLDB, you will need to use the **LLDB: Command Prompt** command i
 
 CodeLLDB can use external LLDB backends instead of the bundled one.  For example, when debugging Swift programs,
 one might want to use a custom LLDB instance that has Swift extensions built in.   In order to use an alternate backend,
-you will need to provide location of the corresponding LLDB dynamic library (which must be v10.0 or later) via
+you will need to provide location of the corresponding LLDB dynamic library (which must be v13.0 or later) via
 **lldb.library** configuration setting.
 
 Where to find the LLDB dynamic library: