The release notes for the critical update Enable Dependency Access Checks In Lightning Components state that access checks will be done on all components when the update is activated. Previously, access checks would only apply to the top level component.
When the critical update is activated, the framework checks the access allowed for the top-level component and each component dependency, including any permissions needed to access each component. When the critical update isn't activated, the framework checks access for the top-level component only.
Step five of the activation steps state to upgrade any managed packages that contain lightning components. This implies that the update applies to managed packages.
- If you have installed any packages that contain a Lightning component, upgrade to the latest version.
I have a managed package that contains lightning components. One component 'GlobalParent' has an access level of 'global'. 'GlobalParent' contains/depends on a non-global component 'PrivateChild'. I'd assume that when I drag 'GlobalParent' onto my community that 'PrivateChild' would fail the access check and I would see an error. I do not see an error.
What does this update actually do?