Just to echo what numerous people have said above: this is clearly a breaking change, and I don’t understand how it’s been rolled out both as part of a minor release, and without any deprecation notices preceding the change.
I appreciate the change makes sense from a security point of view, and that the previous contexts in which get_field worked were strictly speaking “incorrect”, but that doesn’t change the fact that this is a non-backwards compatible API change, which should have been included only as part of a major version release according to semantic versioning standards.
ACF’s versioning has traditionally been robust and reliable, so it’s surprising that has not been the case on this occasion.
