Is your feature request related to a problem? Please describe.
Unit tests are performed on quite outdated versions of CMake (see this run).
Describe the solution you'd like
While we should definitely test on the oldest version of CMake that we plan to support, I think we should also be testing on the latest CMake version (v3.26.3 at the time of writing) since users are more likely to have that than v3.14.7.
The lukka/get-cmake@latestaction is useful for this, since you can specify latest and latestrc in the CMake version matrix in the CI to always fetch the latest stable and release candidates of CMake, respectively.
Describe alternatives you've considered
We could manually change the version matrix when new versions of CMake are released, but if we can automate it, I think we should.
Additional Context
The step needed to use the lukka/get-cmake@latest action would be:
- name: Get latest CMake and Ninja
uses: lukka/get-cmake@latest
with:
cmakeVersion: ${{ env.cmake_version }}
Is your feature request related to a problem? Please describe. Unit tests are performed on quite outdated versions of CMake (see this run).
Describe the solution you'd like While we should definitely test on the oldest version of CMake that we plan to support, I think we should also be testing on the latest CMake version (v3.26.3 at the time of writing) since users are more likely to have that than v3.14.7.
The
lukka/get-cmake@latestaction is useful for this, since you can specifylatestandlatestrcin the CMake version matrix in the CI to always fetch the latest stable and release candidates of CMake, respectively.Describe alternatives you've considered We could manually change the version matrix when new versions of CMake are released, but if we can automate it, I think we should.
Additional Context The step needed to use the
lukka/get-cmake@latestaction would be: