1.22.28

Improvements:

• Updated extension dependencies (ms-vscode.cpp-devtools)

1.22.27

Bug Fixes:

Fix infinite presets reloading loop when preset files are symlinks or include symlinked files. #4668
Reapplying "Refactor and improve colorization language services support" #4697

1.22.26

Features:

• Add bookmarks and filtering of outline view. #4539 @bradphelan
• Add pre-fill project name using current folder name #4533 @HO-COOH
• Add API v5 which adds presets api. #4510 @OrkunTokdemir
• Add an option to extract details about failing tests from CTest output using regular expressions. #4420
• Add output parser for include-what-you-use. PR #4548 @malsyned
• Add better return information in the API. PR #4518

Improvements:

• In the Test Explorer, associate CTest tests with outermost function or macro invocation that calls add_test() instead of with the add_test() call itself. #4490 @malsyned
• Better support of cmake v4.1 and its error index files in cmake-file-api replies #4575 Contributed by STMicroelectronics
• Added support for clang-cl vendor detection: ${buildKitVendor}, ${buildKitVersionMajor}, etc. now expand correctly when using clang-cl on Windows #4524 @wchou158

Bug Fixes:

• Fix Compiler Warnings not shown in Problems Window [#4567]#4567
• Fix bug in which clicking "Run Test" for filtered tests executed all tests instead #4501 @hippo91
• Migrate macOS CI from deprecated macOS-13 to macOS-15 Image #4633
• Ensure Visual Studio developer environment propagation preserves VCPKG_ROOT, enabling vcpkg-dependent configure runs after using the Set Visual Studio Developer Environment command. microsoft/vscode-cpptools#14083
• Fix auto-focusing the "Search" input field in the CMake Cache view. #4552 @simhof-basyskom
• Remove the demangling feature in the code coverage implementation for now since it doesn't work properly. PR #4658
• Fix incorrect IntelliSense configuration when a UTILITY has source files. #4404

1.21.36

Features:

• Add an option to specify the launch target for debugging CTest tests. #4273
• Add a setting to enable/disable our built-in language services. #4290
• Add an option to group the default build target dropdown using CMake groups #3953 @itzandroidtab
• Add cmake.exclude setting that allows users to set folders that they want the CMake Tools extension to ignore. #4112
• Add a command to substitute CMake Cache variables in launch.json and tasks.json. #4422
• Add support for presets v10. #4459, #4445

Improvements:

• Add name de-mangling for C++ symbols in the Test Explorer view when running tests with coverage. #4340 @rjaegers
• No longer convert paths on lowercase on MacOS to enable cpp tools to resolve them. #4325 @tringenbach
• Speedup & reduce heap allocations in shlex split module function. Significant gains for mid-large compile_commands.json - CompilationDatabase construction. #4458 @borjamunozf

Bug Fixes:

• Fix bug that makes Configure Task lists only first folder in workspace. #3232
• Fix displaying "Go to Test" in the Test Explorer when the DEF_SOURCE_LINE property is set, but there is no backtrace information present. #4321 @rjaegers
• Fix gnuld error parsing false positive on make errors, false negative due to trailing \r, and false parsing of new "multiple definitions" error #2864 @0xemgy
• Fixes for small bug string bugs. #4319, #4317, #4312
• Fixes localization for "workspace is" string. #4374
• Make tooltips for selecting Launch/Debug Target. #4373
• Fix bug where unrelated symlinks are read as variant files #4304 @vitorramos.
• Fix evaluation of conditions in presets. #4425
• Fix ENOENT error at vscode startup on some circumstances #2855 Contributed by STMicroelectronics
• Fix repeat execution option in test presets #4443
• Fix bug that makes some build hang #4424 and #4465
• Fix issue with switching to presets during Quick Start. #4409
• Fix bug that shows empty lines in Pinned Commands view. #4406

1.20.53

1.20.53

Improvements:

• Add notification suggesting users to uninstall twxs.cmake now that we have built-in Language Services. #4288

Bug Fixes:

• Fix regression where we weren't properly expanding copyCompileCommands path. #4294

1.20.52

1.20

Features:

• Add support for Presets v9, which enables more macro expansion for the include field. #3946
• Add support to configure default folder in workspace setting. #1078
• Add support to configure default folder in workspace setting. #1078 @sanore
• Add support for processing LCOV based coverage info files when tests are
  executed. This adds test execution type, "Run with coverage", on the ctest
  section of the Testing tab.
  #4040
• Add basic CMake language services: quick hover and completions for CMake built-ins. PR #4204
• Add an option to scan kits from a folder. #4191 @std-microblock

Improvements:

• Add ability to pass custom target to "CMake: Build Target" command as argument. #3598 @hippo91
• Fix "Unable to resolve configuration with compilerPath" issue for Swift. #4097
• Ensure that any uses of proc.spawn work, especially for .bat and .cmd files, due to VS Code updating to Node 20. #4037
• Fix "Test output isn't visible when failed" and also mark skipped tests as so. #4116 @redstrate
• Ensure that stopping tests actually forces the tests to stop running. #2095
• Retire the Show Options Moved Notification #4039
• Improve the pinned commands experience by defaulting settings and using VS Code state rather than modifying user settings. #3977
• Skip project building in the CTest test explorer when cmake.buildBeforeRun is set to false. #4241 @Dabsunter
• Improve consistency in key bindings. #4124 @alex20230721

Bug Fixes:

• Fix issue where files don't show up in the outline if any in the group are generated. #4099
• Fix issue where setting test suite delimiter prevent execution of all tests. #4092 @hippo91
• Fix our setting of isUserPreset for presets, only set it to true if it's defined in a user presets file. #4059
• Fix issue where duplicate presets are being listed in dropdown. #4104
• Ensure that we're sanitizing paths for cmake.copyCompileCommands. #3874
• Ensure that tests are updated after a build. #4148
• Fix various GCC compiler errors and GCC linker errors not showing up in Problems View #2864 @0xemgy
• Fix reloading presets when included files are changed or renamed and updated. #3963
• Fix the usage of toolset and archiecture in presets without generator set. #4181
• Fix compilation database path comparison with the cmake.copyCompileCommands that could otherwise overwrite that file. #4207 @k0zmo
• Fix parsing of CMakeUserPresets.json containing configure preset that is referenced in workflow preset. #4202 @nikobockerman
• Fix auto select active project corner case. #4146 Contributed by STMicroelectronics
• Fix issue where starting a CMake Configure with CMake Debugger while there was already a configure process running left a debug session going without a way to stop it. #4230

1.19.52

1.19.52

Improvements:

• Update signing to support VSCode extension signing. #4055

1.19.51

1.19.51

• Fix generator and preferredGenerator logic. #4031, #4005, #4032

1.19.50

1.19.50

Bug Fixes:

• Fix env expansion of all variables (toolchainFile, etc.) in presets. #4019
• Fix issues with inheritance and presets. #4023

1.19.49

1.19.49

Features:

• Add setting cmake.useVsDeveloperEnvironment to allow for more user control on when the Visual Studio Developer Enviornment is attempted to be added to the CMake Presets environment. #3892

Improvements:

• Add Unspecified option for selecting a kit variant to allow CMake itself to select the build type. #3821
• Skip loading variants when using CMakePresets. #3300
• Resolve diagnostics files relative to workspace and build directory, fixes #1401 @fargies
• Add setting to only show the cmake log on target failure. #3785 @stepeos
• Preset expansion occurs on CMakePresets.json or CMakeUserPresets.json save, and if there are no errors the expanded presets are cached. The VS Developer Environment will only be applied to a preset if it is selected. Expansion errors will show in the problems panel and preset files with errors will be invalid, and any presets they contain cannot be used. #3905
• Remove pop-ups asking to configure, default cmake.configureOnOpen to true. #3967

Bug Fixes:

• Attempt to fix stringifying the extension context. #3797
• Fix issue where cmake.preferredGenerators wasn't falling back to the next entry when the first entry didn't exist. #2709
• Potential fix for attempting to load a non-variants file as a variants file and throwing a parse exception. #3727
• Fix issue where cmakeUserPresets.json not showing up in project outline. #3832
• Fix edge case where parsing tests fails when additional output is printed before tests json. #3750
• Fix issue where Configure with CMake Debugger fails on restart because the previously used pipe to CMake Debugger is no longer available. #3582
• Fix custom kit PATH being overriden. #3849
• Fix debug variables being overriden. #3806
• Fix issue in Quick Start where a C file was generated in place of a C++ file. #3856
• Fix custom build tasks not showing up. #3622
• Fix the bug where if a relative path specified for installDir, it is not calculated relative to the source directory, which is how it should be according to the CMake installDir docs here. #3871
• Fix issue with CMakeLists.txt depth search. #3901
• Fix localized file path for schema files. #3872
• Disable annoy and invalid extenion message about fix windows sdk for MSVC 2022. #3837
• Fix re-using a terminal for launching even when the environment has changed. #3478
• Fix our keybindings for debug and run without debugging to better match VS Code. #3507
• Allow success recovery in the configure precondition handler. #3554
• Prevent second configure after QuickStart if the automaticReconfigure setting is enabled. #3910
• Set usepresets context after manually creating a CMakePresets.json/CMakeUserPresets.json or using QuickStart to create it. #3854
• Only do special handling of ~ for code model reply path on linux. #3957
• Fix issues with expanding unnecessary environment variables and incorrectly saving preset environments to cache. Also fixes expansion error reporting issue with not checking for an invalid Configure preset in other types of presets. #3961 & #1841