Thanks to everyone involved for your work! I have some questions/comments:
If I have something like the following in my CMakePresets.json, do I need to (or might I want to) change anything about it once I’m using CMake 4.2?
{
"name": "tool:emscripten",
"hidden": true,
"description": "available if you set/export EMSDK environment variable. good for IDEs which are hard to configure to use `emcmake cmake`.",
"condition": {"type": "notEquals", "lhs": "$env{EMSDK}", "rhs": ""},
"toolchainFile": "$env{EMSDK}/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake",
If I have an external project that also uses CMake, and the main project gets environment variables from a CMake preset (and I rely on build, install, test, etc. to inherit from the configure preset), what would I need to do to have the external project get the same environment variables? Do I just do nothing, or do I need to manually forward the values for each of configure, build, install, and test?
Some escaping here is missing 
and I got a minor scare before reading what the actual change is in https://cmake.org/cmake/help/latest/policy/CMP0199.html. Much narrower than it sounds here and in the release notes. Maybe a little bit of elaboration could save some other readers from a similar scare?
Out of curiosity, is there an anticipated non-rc release date for CMake 4.2?