PR #2696 replaces the brittle exact-string Dockerfile patch for OpenClaw replaceConfigFile with scripts/rcf_patch.py, which is a real improvement and matches the current openclaw@2026.4.24 compiled shape.
One follow-on hardening gap: the regex is whitespace-tolerant, but still assumes the object passed to tryWriteSingleTopLevelIncludeMutation({...}) lists snapshot before nextConfig: params.nextConfig.
Current order works:
tryWriteSingleTopLevelIncludeMutation({
snapshot,
nextConfig: params.nextConfig
})Equivalent reversed order currently fail-closes:
tryWriteSingleTopLevelIncludeMutation({
nextConfig: params.nextConfig,
snapshot
})That is not a current 2026.4.24 blocker, but it is the same class of future compiled-dist drift this helper is meant to reduce. A good follow-up would make the matcher genuinely order-independent, or narrow the claim/comment so it only promises whitespace tolerance.
@BenediktSchackenberg, thanks again for #2696. If you agree with this follow-up and want to take it, that would be welcome, but no pressure.
PR #2696 replaces the brittle exact-string Dockerfile patch for OpenClaw
replaceConfigFilewithscripts/rcf_patch.py, which is a real improvement and matches the currentopenclaw@2026.4.24compiled shape.One follow-on hardening gap: the regex is whitespace-tolerant, but still assumes the object passed to
tryWriteSingleTopLevelIncludeMutation({...})listssnapshotbeforenextConfig: params.nextConfig.Current order works:
Equivalent reversed order currently fail-closes:
That is not a current
2026.4.24blocker, but it is the same class of future compiled-dist drift this helper is meant to reduce. A good follow-up would make the matcher genuinely order-independent, or narrow the claim/comment so it only promises whitespace tolerance.@BenediktSchackenberg, thanks again for #2696. If you agree with this follow-up and want to take it, that would be welcome, but no pressure.