chore: update yarn to v3.8.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
yarn (source)	3.2.0 -> 3.8.2

---

Release Notes

yarnpkg/berry (yarn)

v3.8.2

Compare Source

v3.8.1

Compare Source

v3.8.0

Compare Source

v3.7.0

Compare Source

v3.6.4

Compare Source

v3.6.3

Compare Source

v3.6.2

Compare Source

v3.6.1

Compare Source

v3.6.0

Compare Source

v3.5.1

Compare Source

v3.5.0

Compare Source

v3.4.1

Compare Source

• Fixes an accidental backport error in yarn init.

v3.4.0

Compare Source

Node.js parity

• PnP now supports the Node --conditions flag.
• PnP now supports the Node --watch flag on Node 18 (it previously only supported it on Node 19).

Bugfixes

• The PnP API module (pnpapi) can now be imported from ESM modules.
• ZipFS.prototype.getBufferAndClose will not error on empty archives resulting from an unlink after write.
• Fixes various issues around postinstall script inter-dependencies.
• Removes the message prefixes (YN0000) from yarn workspaces foreach.

Compatibility

• Updates the PnP compatibility layer for TypeScript v5.0.0-beta.

v3.3.1

Compare Source

v3.3.0

Compare Source

Installs

• The node-modules linker avoids creation of circular symlinks
• The node-modules linker no longer creates duplicate copies inside of aliased packages
• The node-modules linker locates binaries correctly when the same version of the package is duplicated inside root workspace and another workspace
• Improved performance for hardlinks-global node-modules linker mode by 1.5x

Compatibility

• Updates the PnP compatibility layer for TypeScript v4.9.2-rc.

v3.2.4

Compare Source

Compatibility

• The patched filesystem now supports fchown.
• PnP now handles private import mappings.
• Updates the PnP compatibility layer for TypeScript v4.8.4 and v4.9.1-beta.
• PnP now reports loaded modules when in watch mode.

v3.2.3

Compare Source

Bugfixes

• When Corepack is enabled Yarn will now use the current CLI to prepare external Yarn classic projects, matching the behaviour of when Corepack is disabled.

Compatibility

• Updates the PnP compatibility layer for TypeScript 4.8.1-rc
• The ESM loader now supports unflagged JSON modules.

v3.2.2

Compare Source

Compatibility

• The patched filesystem now supports ftruncate.
• The patched filesystem now supports fchmod.
• The patched filesystem now supports throwIfNoEntry.
• The PnP filesystem now handles most of the FileHandle methods
• Updates the PnP compatibility layer for TypeScript 4.8 Beta
• The npm_package_json environment variable is now set by Yarn.

v3.2.1

Compare Source

Installs

• The pnpm linker no longer tries to remove node_modules directory, when node-modules linker is active
• The node-modules linker does not fail anymore if portal dependency points to an external project with multiple interdependent workspaces
• The node-modules linker has received various improvements:
  • applies hoisting algorithm on aliased dependencies
  • reinstalls modules that have their directories removed from node_modules by the user
  • improves portal hoisting
  • supports supportedArchitectures

Bugfixes

• The PnP ESM loader is now able to handle symlinked extensionless entrypoints.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22762
    throw new Error(
          ^

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22762:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22776:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:24232:5) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22756:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22776:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22703:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22826:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23433:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23525:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:24232:5)
}