Comment 9 for bug 1943288

Matthias has communicated out of band that the regressions were not due to new features in the upstream code, but due to a misconfiguration of the build. That has now been addressed, and with my release team hat I don't see any further cause for concern.

The feature freeze is meant to ensure review of new features, not just of all new upstream code. I don't see any evidence that there are new features here. (exec-static-tramp may be a new feature, but it has now been - correctly - disabled in the build.)