I’m not sure, but we have manually intervened in the update process. Maybe it’s causing the core/shipped.js issue in return. Just guessing though, but I never ran into that issue so far and always restored default ownership/ permission before the update and didn’t use strong permissions at last since NC12.