Hi,
You can safely ignore this error, it popped up during the automated update process during the replacement and will not replicate again.
In the new version some files were moved to a different namespace and momentarily when the WordPress updater replaced them an existing hook was still running referencing the old locations.