- Fix a bug where the first argument for pre/post-configure args didn't have the proper spacing in front of it [PR #530](https://github.com/microsoft/vscode-makefile-tools/pull/530)
- Fix a bug where we weren't handling pre/post-configure args for the non-windows scenarios. [#531](https://github.com/microsoft/vscode-makefile-tools/issues/531)
- Add support for post-configure and pre-configure script arguments, both globally and per configuration. [#151](https://github.com/microsoft/vscode-makefile-tools/issues/151)
- Ship the parseCompilerArgs script with the extension to avoid race conditions. [#516](https://github.com/microsoft/vscode-makefile-tools/issues/516), [#475](https://github.com/microsoft/vscode-makefile-tools/issues/475)
- Avoid relativizing paths in the project outline. [#519](https://github.com/microsoft/vscode-makefile-tools/pull/519) [@drok sponsored by @Mergesium](https://github.com/drok)
- Improve the UI user experience when key pieces (makefile, make, build.log) are not found. [#394](https://github.com/microsoft/vscode-makefile-tools/issues/394)
- Add support for C++23 [#433](https://github.com/microsoft/vscode-makefile-tools/issues/433)
- Smart path handling and flexibility in required path structure/default for various path settings (makefilePath, miDebuggerPath). [#341](https://github.com/microsoft/vscode-makefile-tools/issues/341) [#365](https://github.com/microsoft/vscode-makefile-tools/issues/365)
Bug fixes:
- Fix case sensitivity on Windows. [#416](https://github.com/microsoft/vscode-makefile-tools/issues/416)
- Avoid regexp hang when processing strings like "-------------". [#106](https://github.com/microsoft/vscode-makefile-tools/issues/106)
- Ensure that we don't write into user settings when a value has been specified by the user. [#356](https://github.com/microsoft/vscode-makefile-tools/pull/356)
- Don't configure when there is no makefile entrypoint. Don't cache when provider data is empty. [#449](https://github.com/microsoft/vscode-makefile-tools/issues/449)
- Log about telemetry only when it is enabled in VSCode. [#446](https://github.com/microsoft/vscode-makefile-tools/issues/446)
- Do not write to the user's workspace folders by default. [#329](https://github.com/microsoft/vscode-makefile-tools/issues/329)
- Do not change the value of makefile.extensionOutputFolder in the user's workspace/folder settings. [#331](https://github.com/microsoft/vscode-makefile-tools/issues/331)
- Implement the ability to make various extension features optional and hide them from the UI. Initial examples: debugging an executable target and/or running it in terminal. [#290](https://github.com/microsoft/vscode-makefile-tools/issues/290) [@jdmchp](https://github.com/jdmchp)
Bug fixes:
- Fix telemetry bug related to object settings. [PR #309](https://github.com/microsoft/vscode-makefile-tools/pull/309)
- Fix localize initialization logistics in launch source code. [#305](https://github.com/microsoft/vscode-makefile-tools/issues/305)
- Fix regular expression used in processing the build targets ouf of the dryrun log. [PR #307](https://github.com/microsoft/vscode-makefile-tools/pull/307) [@DepthDeluxe](https://github.com/DepthDeluxe)
- Fix makePath: add "make" when only a directory path was specified. [#237](https://github.com/microsoft/vscode-makefile-tools/issues/237)
- Activation problem when buildLog is used. Add missing linker. Fix bug when calculating binary targets. Use non deprecated VSCode terminal setting. [PR #256](https://github.com/microsoft/vscode-makefile-tools/pull/256)
- Keep the pre-configure environment when sending the launch target to the terminal or the debugger. [#295](https://github.com/microsoft/vscode-makefile-tools/issues/295)
- Honor the "terminal.integrated.automationShell" setting when spawning make for configure. [#233](https://github.com/microsoft/vscode-makefile-tools/issues/233)
- Remove the "build" button icon from other UIs than the main Makefile Tools panel. [#245](https://github.com/microsoft/vscode-makefile-tools/issues/245)
- The build task fails for projects using -f or -C (makefile not in root) because of quoting. [#249](https://github.com/microsoft/vscode-makefile-tools/issues/249)
- Fix activation for makefiles below the root. [#248](https://github.com/microsoft/vscode-makefile-tools/issues/248)
- Support for problem matchers. [#7](https://github.com/microsoft/vscode-makefile-tools/issues/7)
Bug fixes:
- Fix wrong extension activation for non makefile projects. [#181](https://github.com/microsoft/vscode-makefile-tools/issues/181)
- Align defaults for C/C++ standard and IntelliSense mode to expectations in CMakeTools/CppTools. [#119](https://github.com/microsoft/vscode-makefile-tools/issues/119)
- Fix parsing source file paths when in quotes. [#203](https://github.com/microsoft/vscode-makefile-tools/issues/203)
- Don't show the Makefile Tools output channel automatically. [#115](https://github.com/microsoft/vscode-makefile-tools/issues/115)
- Improve parsing of more complicated scenarios of quoting and escaping for -D and -I. [#169](https://github.com/microsoft/vscode-makefile-tools/issues/169)
- Pass pre-configure environment to the build task. [PR #104](https://github.com/microsoft/vscode-makefile-tools/pull/239)
- Complete the parsing input text with what is outputted on stderr as well, besides stdout. [PR #238](https://github.com/microsoft/vscode-makefile-tools/pull/238)
- Fix paths processing for non-windows tools run on windows outside MinGW/CygWin environments. [#219](https://github.com/microsoft/vscode-makefile-tools/issues/219)
- Fix pre-configure script invocation, broken on Linux starting with Makefile Tools 0.2.1. [#170](https://github.com/microsoft/vscode-makefile-tools/issues/170) [@avrahamshukron](https://github.com/avrahamshukron)