Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ensure we apply our presets to local cache #3503

Merged
merged 5 commits into from
Jan 2, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
update changelog
  • Loading branch information
gcampbell-msft committed Dec 20, 2023
commit 6e3935d1ed161998bcaac420be587da88a9c7d43
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Bug Fixes:
- Ensure that the output is cleared for `debugTarget` and `launchTarget`. [#3489](https://github.com/microsoft/vscode-cmake-tools/issues/3489)
- Fix the inheritance of the `environment` for CMakePresets. [#3473](https://github.com/microsoft/vscode-cmake-tools/issues/3473)
- Removed an unnecessary `console.assert`. [#3474](https://github.com/microsoft/vscode-cmake-tools/issues/3474)
- Make sure that we apply our presets to the local cache before also adding a build preset and erroneously overwriting our change. [#3376](https://github.com/microsoft/vscode-cmake-tools/pull/3503)
- Make sure that we apply our presets to the local cache before also adding a build preset and erroneously overwriting our change. [#3376](https://github.com/microsoft/vscode-cmake-tools/issues/3376)

## 1.16.32
Improvements:
Expand Down
Loading