●Change8

Yarn

Dev Tools

πŸ“¦πŸˆ Active development trunk for Yarn βš’

Latest: @yarnpkg/cli/4.12.014 releases3 common errorsView on GitHub

Release History

@yarnpkg/cli/4.12.02 fixes1 feature
Nov 23, 2025

This release adds npm web login support and includes fixes for git clone argument handling and JSON Schema.

@yarnpkg/cli/4.11.02 fixes6 features
Nov 7, 2025

Yarn 4.11.0 adds PnP read support for TypedArray/DataView, resolvesFilename conditions, a DURATION settings type, environment variable escaping, and catalog improvements, while fixing publish JSON output and GitLab CI OIDC detection.

@yarnpkg/cli/4.10.33 fixes1 feature
Sep 23, 2025

Yarn Berry 4.10.3 introduces bug fixes for OIDC publishing, npmMinimalAgeGate handling, and protocol removal, and adds support for pnpm postinstall scripts.

@yarnpkg/cli/4.10.21 fix1 feature
Sep 18, 2025

This release busts the metadata cache and adds support for registries without publish times via minimalAgeGate.

@yarnpkg/cli/4.10.11 fix
Sep 18, 2025

Patch release 4.10.1 fixes publishing archives.

@yarnpkg/cli/4.10.01 fix3 features
Sep 18, 2025

Yarn Berry 4.10.0 adds catalog support, new npm config options, and OIDC authentication for CI, while updating TypeScript to 5.9 and fixing a documentation typo.

@yarnpkg/cli/4.9.42 fixes
Aug 26, 2025

This release (4.9.4) includes bug fixes for hash validation in plugin-essentials and aligns `yarn version pre*` behavior with the documentation.

@yarnpkg/cli/4.9.35 fixes4 features
Aug 20, 2025

Yarn Berry 4.9.3 introduces provenance support, a new GIT_AUTHOR_NAME test env variable, and dry‑run/json flags for npm publish, while fixing several platform detection and TypeScript issues and deprecating the `-v` flag for `yarn config`.

@yarnpkg/cli/4.9.26 fixes3 features
Jun 3, 2025

Yarn 4.9.2 updates Docusaurus to 3.7, de‑duplicates the chalk dependency, adds hpagent for proxy support, and includes several bug fixes and improvements.

@yarnpkg/cli/4.9.12 fixes
Apr 11, 2025

Yarn Berry 4.9.1 includes fixes for a pnpm install performance regression and resolves metadata filename ambiguities.

@yarnpkg/cli/4.9.03 features
Apr 9, 2025

Yarn Berry 4.9.0 adds an experimental JavaScript zip parser for the PnP hook, introduces npm provenance support, and adds support for the `jsr:` protocol.

@yarnpkg/cli/4.8.11 fix
Mar 30, 2025

This patch release (4.8.1) fixes a memory leak introduced in version 4.8.0.

@yarnpkg/cli/4.8.08 fixes5 features
Mar 28, 2025

This release adds argument support to yarn init, new pnpm store configuration, version apply exact, and several bug fixes and performance improvements.

@yarnpkg/cli/4.7.08 fixes1 feature
Mar 1, 2025

This release primarily includes bug fixes, an improvement to the yarn init command, and an upgrade of ESLint to version 9 with required configuration migration.

Common Errors

QueryFailedError1 report

"QueryFailedError" in Yarn often arises from incompatible or outdated dependencies within a monorepo, particularly when using Plug'n'Play (PnP). To resolve it, ensure that shared packages are correctly hoisted to the top-level node_modules and that all packages requiring those dependencies point to the hoisted versions. Consider updating Yarn to the latest version, clearing the Yarn cache, and regenerating the lockfile to reconcile dependency versions across the monorepo.

MaxRedirectsError1 report

The "MaxRedirectsError" in yarn often occurs when yarn or npm encounters too many HTTP redirects while trying to download a package, typically due to misconfigured registries or network issues. To fix this, try clearing the yarn cache using `yarn cache clean`, and then explicitly set the correct registry using `yarn config set registry <your_registry_url>`, or try using npm with `npm config set registry <your_registry_url>`. If this doesn't work, investigate potential network proxy issues that might be causing the redirects.

UnsupportedProtocolError1 report

The "UnsupportedProtocolError" in yarn often arises from outdated yarn versions or when yarn tries to access registries using unsupported protocols like `git+ssh`. Upgrade yarn to the latest version using `npm install -g yarn` or explicitly configure yarn to use `https` by setting the registry URL via `yarn config set registry https://registry.npmjs.org`. Also, inspect your `.yarnrc` file and dependencies' URLs for incorrect or git-based protocols and change these to `https`.

Related Dev Tools Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed