chore(yarn-cli): update bundled yarn

[TorinAsakura]

Таска

• Close [Feature] Обновить bundled Yarn до актуальной версии #622

Как проверять

Основной сценарий

1. Контекст: локальный checkout ветки feature/update-bundled-yarn, Rosetta Node /usr/local/bin/node, bundled Yarn .yarn/releases/yarn.mjs.
   Действие: запустить /usr/local/bin/node .yarn/releases/yarn.mjs workspace @atls/yarn-cli build.
   Ожидаемый результат: сборка завершается успешно, в выводе есть SchematicFactory build successed, js-yaml PnP resolution error из [Bug] Убрать js-yaml PnP error из сборки CLI #620 не воспроизводится.

Дополнительный сценарий

1. Контекст: локальный checkout ветки feature/update-bundled-yarn, Rosetta Node /usr/local/bin/node.
   Действие: запустить проверки из блока ниже.
   Ожидаемый результат: команды завершаются с exit code 0; install --immutable не требует lockfile-правок; yarn/cli/dist/yarn.mjs и .yarn/releases/yarn.mjs byte-identical; release workspaces @atls/code-configuration и @atls/code-pack собираются на обновлённом toolchain.

Пруфы

• Rosetta version smoke

/usr/local/bin/node .yarn/releases/yarn.mjs -v
# 1.1.67-atls

• immutable install

/usr/local/bin/node .yarn/releases/yarn.mjs install --immutable
# exit 0; existing peer/build-script warnings only

• release workspaces from failed checks

/usr/local/bin/node .yarn/releases/yarn.mjs workspace @atls/code-configuration build
/usr/local/bin/node .yarn/releases/yarn.mjs workspace @atls/code-pack build
# exit 0

• changed workspace builds

/usr/local/bin/node .yarn/releases/yarn.mjs workspaces changed foreach -t run build
# exit 0; Done in 7m 4s

• typecheck

/usr/local/bin/node .yarn/releases/yarn.mjs typecheck yarn code
# exit 0; 226 files

• raijin checks

/usr/local/bin/node .yarn/releases/yarn.mjs raijin:check
# exit 0

• lint

/usr/local/bin/node .yarn/releases/yarn.mjs lint cli/cli-ui-test-progress/src/test-progress-bar.component.tsx cli/cli-ui-test-progress/src/test-progress-files.component.tsx code/code-test/src/tester.ts yarn/plugin-checks/sources/abstract-checks-test.command.test.ts yarn/plugin-checks/sources/abstract-checks-test.command.ts yarn/plugin-checks/sources/test-results.formatter.ts yarn/plugin-test/sources/abstract-test.command.tsx
# exit 0

• unit smoke

COMMAND_PROXY_EXECUTION=true /usr/local/bin/node .yarn/releases/yarn.mjs test unit -t yarn/plugin-checks
# exit 0; 6 pass / 0 fail / 8 total / 3 files

COMMAND_PROXY_EXECUTION=true /usr/local/bin/node .yarn/releases/yarn.mjs test unit -t code/code-test
# exit 0; 0 pass / 0 fail / 0 total / 0 files

COMMAND_PROXY_EXECUTION=true /usr/local/bin/node .yarn/releases/yarn.mjs test unit -t yarn/plugin-test
# exit 0; 0 pass / 0 fail / 0 total / 0 files

• bundle sync

cmp -s yarn/cli/dist/yarn.mjs .yarn/releases/yarn.mjs
# exit 0

• whitespace check, excluding generated bundled Yarn files

git diff --check -- ':!yarn/cli/dist/yarn.mjs' ':!.yarn/releases/yarn.mjs'
# exit 0

[TorinAsakura]

@codex

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".