renovate[bot]
commented
8 months ago âš 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
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0001: │ Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
at PassThrough.onclose (node:internal/streams/end-of-stream:154:30)
at PassThrough.emit (node:events:518:28)
at emitCloseNT (node:internal/streams/destroy:147:10)
at process.processTicksAndRejections (node:internal/process/task_queues:81:21)
➤ YN0013: │ No packages were cached - 2 packages had to be fetched
➤ YN0000: └ Completed in 0s 900ms
➤ YN0000: Failed with errors in 1s 81ms
coderabbitai[bot]
This PR contains the following updates:
3.0.0-rc.9->3.0.2Release Notes
yarnpkg/berry (yarn)
### [`v3.0.2`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#302) - Updated TypeScript patch to cover TypeScript 4.4. - Fixed `VirtualFS.mapToBase` to preserve `.` characters (was converting them to empty strings). ### [`v3.0.1`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#301) - Fixes an edge case with the PnP loader when calling `readdir` with `null` as second parameter (instead of `undefined`). ### [`v3.0.0`](https://togithub.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#300) ##### **Breaking Changes** - Node 10 isn't supported anymore. - Plugins can't access `yup` anymore (we migrated to [Typanion](https://togithub.com/arcanis/typanion) as part of [Clipanion v3](https://togithub.com/arcanis/clipanion)). - To upgrade `workspace-tools`, remove it from your `.yarnrc.yml`, upgrade, then import it back. - The `enableImmutableInstalls` will now default to `true` on CI (we still recommend to explicitly use `--immutable` on the CLI). - You can re-allow mutations by adding `YARN_ENABLE_IMMUTABLE_INSTALLS=false` in your environment variables. - The `initVersion` and `initLicense` configuration options have been removed. `initFields` should be used instead. - Yarn will now generate `.pnp.cjs` files (instead of `.pnp.js`) when using PnP, regardless of what the `type` field inside the manifest is set to. - The virtual folder (used to disambiguate peer dependencies) got renamed from `$$virtual` into `__virtual__`. - The `-a` alias flag of `yarn workspaces foreach` got removed; use `-A,--all` instead, which is strictly the same. - The old PnPify SDK folder (`.vscode/pnpify`) won't be cleaned up anymore. - The `--skip-builds` flag from `yarn install` got renamed into `--mode=skip-build`. - The `bstatePath` configuration option has been removed. The build state (`.yarn/build-state.yml`) has been moved into the install state (`.yarn/install-state.gz`) - The cache files need to be regenerated. We had to change their timestamps in order to account for a flaw in the zip spec that was causing problems with some third-party tools. - `@yarnpkg/pnpify` has been refactored into 3 packages: - `@yarnpkg/sdks` now contains the [Editor SDKs](https://yarnpkg.com/getting-started/editor-sdks) - `@yarnpkg/pnpify` now contains the [PnPify CLI compatibility tool that creates in-memory `node_modules`](https://yarnpkg.com/advanced/pnpify) - `@yarnpkg/nm` now contains the `node_modules` tree builder and hoister - `@yarnpkg/plugin-node-modules` has been renamed to `@yarnpkg/plugin-nm` - The `--clipanion=definitions` commands supported by our CLIs will now expose the definitions on the entry point (rather than on `.command`) ##### API - `structUtils.requirableIdent` got removed; use `structUtils.stringifyIdent` instead, which is strictly the same. - `configuration.format` got removed; use `formatUtils.pretty` instead, which is strictly the same, but type-safe. - `httpUtils.Options['json']` got removed; use `httpUtils.Options['jsonResponse']` instead, which is strictly the same. - `PackageExtension['description']` got removed, use `formatUtils.json(packageExtension, formatUtils.Type.PACKAGE_EXTENSION)` instead, which is strictly the same. - `Project.generateBuildStateFile` has been removed, the build state is now in `Project.storedBuildState`. - `Project.tryWorkspaceByDescriptor` and `Project.getWorkspaceByDescriptor` now match on virtual descriptors. ##### Installs - Workspaces now get self-references even when under the `node-modules` linker (just like how it already worked with the `pnp` linker). This means that a workspace called `foo` can now safely assume that calls to `require('foo/package.json')` will always work, removing the need for [absolute aliases](https://nextjs.org/docs/advanced-features/module-path-aliases) in the majority of cases. - The node-modules linker now does its best to support the `portal:` protocol. This support comes with two important limitations: - Projects that make use of such dependencies will have to be run with the `--preserve-symlinks` Node option if they wish to access their dependencies. - Because Yarn installs will never modify files outside of the project due to security reasons, sub-dependencies of packages with `portal:` must be hoisted outside of the portal. Failing that (for example if the portal package depends on something incompatible with the version hoisted via another package), the linker will produce an error and abandon the install. - The node-modules linker can now utilize hardlinks. The new setting `nmMode: classic | hardlinks-local | hardlinks-global` specifies which `node_modules` strategy should be used: - `classic` - standard `node_modules` layout, without hardlinks - `hardlinks-local` - standard `node_modules` layout with hardlinks inside the project only - `hardlinks-global` - standard `node_modules` layout with hardlinks pointing to global content storage across all the projects using this option ##### Bugfixes - Yarn now has a proper [governance model](https://togithub.com/yarnpkg/berry/blob/master/GOVERNANCE.md). - The `node-modules` linker will now ensure that the generated install layouts are terminal, by doing several rounds when needed. - The `node-modules` linker will no longer print warnings about postinstall scripts when a workspace depends on another workspace listing install scripts. - Peer dependencies depending on their own parent are now properly hoisted by the node-modules linker. - Boolean values will be properly interpreted when specified inside the configuration file via the `${ENV_VAR}` syntax. - Should any of `preinstall`, `install`, `postinstall` fail, the remaining scripts will be skipped. - The `git:` protocol will now default to fetching `HEAD` (rather than the hardcoded `master`). - The `SIGTERM` signal will now be propagated to child processes. - The PnP linker now schedules packages to be rebuilt if their unplugged folder is removed - `yarn config unset` will now correctly unset non-nested properties - The TypeScript SDK now - And a bunch of smaller fixes. ##### Settings - Various `initFields` edge cases have been fixed. - The `preferAggregateCacheInfo` flag will now also aggregate cleanup reports. - A new `enableMessageNames` flag can be set to `false` to exclude the `YNxxxx` from the output. ##### Commands - `yarn init` can now be run even from within existing projects (will create missing files). - `yarn init` and `yarn set version` will set the `packageManager` field. - `yarn set version` now downloads binaries from the official Yarn website (rather than GitHub). - `yarn set version from sources` will now upgrade the builtin plugins as well unless `--skip-plugins` is set. - `yarn version apply` now supports a new `--prerelease` flag which replaces how prereleases were previously handled. - `yarn run` should be significantly faster to boot on large projects. - `yarn workspaces foreach --verbose` will now print when processes start and end, even if they don't have an output. - `yarn workspaces foreach` now supports a `--fromConfiguration
📅 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.
This PR has been generated by Mend Renovate. View repository job log here.