Apparently yarn just released version 4.1.1 which calculates some package checksums differently than before.
This made all workflows fail during the install phase. To align the yarn versions used in the CI pipeline and in local development, i removed the yarn set version 4.x step from all relevant workflows. corepack will use whatever yarn binary is stored in our repo / configured in our .yarnrc automatically.
CI Pipeline Fix
Apparently yarn just released version 4.1.1 which calculates some package checksums differently than before. This made all workflows fail during the install phase. To align the yarn versions used in the CI pipeline and in local development, i removed the yarn set version 4.x step from all relevant workflows. corepack will use whatever yarn binary is stored in our repo / configured in our .yarnrc automatically.