[Pharo-users] Issues with build: 160, commit: b84a1e1 of the Pharo 7.0.3 image?

Hi, I just launched a new Pharo 7.0 - 32bit (stable) from the pharo launcher. Got back an image from build: 160, commit: b84a1e1 First issue I noticed was a broken (?) component in the Wellcome screen (red block with yelllow border and diagonals). Then, after insalling Seaside and trying to add a new adaptor (via the Seaside launcher), an instance of MenuItemPresenter did not understand #isEnabled. No of these issues are present in a clean image obtained with the zeroconf script (build: 158, commit: 0903ade image). Is anyone else experiencing the same problem? Do templates update automatically when a new build is available? Yours, Alejandro