Skip to content

Release 2.1.207 (2026-08-27)

Bug fixes

  • ignore Conan CMakeDeps per-package files in the baseline (#2908) (#2913) The baseline Conan block (#2878) covered Conan's generic generator output but not its per-package CMakeDeps files, which are also written to the source root. After a single conan install in mq-protocol-gateway (dep gtest/1.15.0), these were left untracked and none matched the baseline:

FindGTest.cmake, GTestConfig.cmake, GTestConfigVersion.cmake, GTestTargets.cmake, GTest-Target-debug.cmake, GTest-debug-armv8-data.cmake, module-GTest-Target-debug.cmake, module-GTest-debug-armv8-data.cmake, module-GTestTargets.cmake

They carry the package name and build type/arch, so they are matched by shape, not an enumerable list. Adds seven globs to the baseline C/C++ Conan block (Find.cmake, Config.cmake, ConfigVersion.cmake, Targets.cmake, -Target-.cmake, -data.cmake, module-.cmake) covering all nine, and mirrors them into this repo's own .gitignore to satisfy the baseline-subset drift guard (test_baseline_is_subset_of_flagship_gitignore).

Judgment call: Find/​Config/​ConfigVersion/​Targets are also names CMake uses for authored or installed package-config files, but those live under cmake/ or are generated into build/, never committed loose at the repo root where Conan writes these - so the residual collision risk is negligible.

Follow-up to #2878. The durable cure for the whole class is redirecting Conan output under build/ (already ignored) rather than the source root - a cpp build-convention change, out of scope here.

CI Evidence: All gates passed — full audit bundle available. Download →