Yes, quite a few extensions were impacted by this problem.
The most common workaround (to be applied on the extension) is to use the 12.10-1 version of the contrib parent instead of 12.10, or apply the same workaround.
Yes, quite a few extensions were impacted by this problem.
The most common workaround (to be applied on the extension) is to use the 12.10-1 version of the contrib parent instead of 12.10, or apply the same workaround.