onPreferenceChange closure is now nonIsolated?

Running up Xcode 16.2 Beta 1, a lot of my code that used onPreferenceChange in Views to change @State properties of those views, such as some notion of a measured width is now complaining about mutating the @MainActor-isolated properties from Sendable closures.

Now I've got to hoop-jump to change @State properties from onPreferenceChange? OK, but seems a bit of extra churn.

onPreferenceChange closure is now nonIsolated?
 
 
Q