Yarn install fails in "composer (next major)" job

Due to this most likely: 📌 Update from Yarn 1 to Yarn 4 RTBC

See the commit: https://git.drupalcode.org/project/drupal/-/commit/ad10de38dd663cf7d6fc0...

Images have not changed nor need changing, just the way to call some things.

Ready to review.

MR: https://git.drupalcode.org/project/gitlab_templates/-/merge_requests/157
Pipeline: https://git.drupalcode.org/project/gitlab_templates/-/pipelines/122312

It all seems to work for current, future, and past versions using the alternative syntax for the yarn command.

Confirm I am running into this, just trying to get gitlab-ci configured for my module including next major version. My module doesn't have a package.json, so the failure seems unrelated to the module itself.

Yes, this should work. corepack enable only has to be run once and then the change is permanent (inside the container/environment at least) so ideally we can get this enabled in the base container and then the scripts can become simpler. Once this is done by default yarn uses Yarn 1 but will automatically switch if a packageManager key is set in package.json, which is what we have done in core for Yarn 4 in Drupal 11.

Merged. Marking as fixed. I will create a new release with this change as it breaks existing integrations.

Amazing, thank you for that quick fix!

Automatically closed - issue fixed for 2 weeks with no activity.