saluu/darkness-dependent-vision
0
0
Fork 0
Code Issues 1 Pull requests 17 Packages Projects Releases 18 Activity

chore(deps): update yarn to v4 #7

Open
renovate-bot wants to merge 1 commit from renovate/major-yarn-monorepo into master
pull from: renovate/major-yarn-monorepo
merge into: saluu:master
Conversation 1 Commits 1 Files changed 5 +2966 -2947
renovate-bot commented 2023-10-22 20:57:55 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
yarn 3.7.0 -> 4.2.2 age adoption passing confidence

Release Notes

yarnpkg/berry (yarn)

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

  • Tweaks -,--verbose in yarn workspaces foreach; -v will now only print the prefixes, -vv will be necessary to also print the timings.

  • Adds a new --json option to yarn run when called without script name

  • Fixes node-modules linker link: dependencies mistreatment as inner workspaces, when they point to a parent folder of a workspace

  • Fixes spurious "No candidates found" errors

  • Fixes missing executable permissions when using nodeLinker: pnpm

  • Fixes packages being incorrectly flagged as optional

  • Fixes cache key corruptions due to uncontrolled git merges

  • Fixes yarn version apply --all --dry-run making unexpected changes

  • Fixes yarn npm login when the remote registry is Verdaccio

v4.0.2

Compare Source

v4.0.1

Compare Source

  • Fixes creation of symlinks for node-modules linker when inner workspace depends on outer workspace
  • Fixes progress bars when the terminal is too large
  • Fixes crashes while running Yarn within Docker within GitHub Actions
  • Fixes yarn npm audit --ignore NUM which didn't apply to deprecations
  • Fixes yarn npm audit --json which didn't print the right output format
  • Fixes an incorrect type export in @yarnpkg/core
  • Implements back the yarn explain peer-requirements command

v4.0.0

Compare Source

Major Changes

  • With Node.js 16's now being End of Life'd, we dropped support for Node.js versions lower than 18.12.

  • Some important defaults have changed:

    • yarn init and yarn set version will prefer using packageManager rather than yarnPath when possible (when they detect COREPACK_ROOT in your environment variables).

    • yarn init will no longer use zero-install by default. You still can enable it, but it should make it easier to start one-of projects without having to rewrite the configuration afterwards.

      • As a result, enableGlobalCache now defaults to true. If your project uses Zero-Installs, the first yarn install you run after migrating to 4.0 will automatically set enableGlobalCache: false in your local .yarnrc.yml.

    • yarn workspaces foreach now requires one of --all, --recursive, --since, or --worktree to be explicitly specified; the previous default was --worktree, but it was rarely what users expected.

    • compressionLevel now defaults to 0 rather than mixed. It's been proved significantly faster on installs, and the size impact was reasonable enough to change the default. Note that it benefits you even if you use Zero-Installs: as per our tests, a zero-compression is actually easier to handle for Git (you can see by yourself with those examples using compressionLevel: 0 vs compressionLevel: mixed).

      • To avoid making the upgrade too disruptive, Yarn will check whether Zero-Installs are enabled the first time you run yarn install after migrating from 3.6 to 4.0. If you do, it will automatically set the old default (compressionLevel: mixed) in your .yarnrc.yml file. You can then remove it whenever you feel ready to actually change the compression settings.

  • All official Yarn plugins are now included by default in the bundle we provide. You no longer need to run yarn plugin import for official plugins (you still need to do it for third-party plugins, of course).

    • This doesn't change anything to the plugin API we provide, which will keep being maintained.
    • Yarn still has a modular architecture and uses the exact same APIs as contrib plugins; all that changes is how we distribute our own features.

  • Yarn's UI during installs has been greatly improved:

    • Packages added and removed from the lockfile are now explicitly reported.
    • Fluctuations in the project cache size are now reported as a single line.
    • Unactionable warnings (node-gyp and transitive peer dependency errors) have been removed.
    • Skipped builds are now only reported during initial installs and manual yarn rebuild calls.
    • The Yarn version is now displayed on installs to help us investigate issues when reported as screenshots.
    • Deprecation checks have been moved to yarn npm audit.

  • Some settings were renamed or removed:

    • caFilePath is now httpsCaFilePath
    • preferAggregateCacheInfo has been removed (it's now always on)
    • pnpDataPath has been removed to adhere to our new PnP specification. For consistency, all PnP files will now be hardcoded to a single value so that third-party tools can implement the PnP specification without relying on the Yarn configuration.

  • The yarn npm audit command has been reimplemented:

    • The audit registry must now implement the /-/npm/v1/security/advisories/bulk endpoint.
    • The npmAuditRegistry can be used to temporarily route audit queries to the npm registry.
    • Deprecations are now returned by default. To silence them, use yarn npm audit ! --no-deprecations.

  • Some legacy layers have been sunset:

    • Plugins cannot access the Clipanion 2 APIs anymore (upgrade to Clipanion 3)
    • Plugins cannot access the internal copy of Yup anymore (use Typanion instead)
    • Yarn will no longer remove the old Yarn 2.x .pnp.js file when migrating.
    • The --assume-fresh-project flag of yarn init has been removed.
API Changes

The following changes only affect people writing Yarn plugins:

  • The ZipFS and ZipOpenFS classes have been moved from @yarnpkg/fslib to @yarnpkg/libzip. They no longer need or accept the libzip parameter.

    • Reading the zip archives is now done on the Node.js side for performance; as a result, the open, ZIP_CREATE, and ZIP_TRUNCATE bindings are no longer needed for ZipFS and have also been removed.

  • The dependencies field sent returned by Resolver#resolve must now be the result of a Configuration#normalizeDependencyMap call. This change is prompted by a refactoring of how default protocols (ie npm:) are injected into descriptors. The previous implementation caused various descriptors to never be normalized, which made it difficult to know what were the descriptors each function should expect.

    • Similarly, the descriptors returned by Resolve#getResolutionDependencies are now expected to be the result of Configuration#normalizeDependency calls.

    • Note that this only applies to the dependencies field; the peerDependencies field is unchanged, as it must only contains semver ranges without any protocol (with an exception for workspace:, but that's not relevant here).

  • The Resolve#getResolutionDependencies function must now return an object of arbitrary string keys and descriptor values (instead of a map with DescriptorHash keys). Those descriptors will be resolved and assigned to the same keys as the initial object. This change allows resolvers to wrap resolution dependencies from other resolvers, which wasn't possible before since it'd have caused the key to change.

  • The generateLoader function in @yarnpkg/pnp no longer generates the $$SETUP_STATE function, it now needs to be present in the loader passed to the function.

  • The getCustomDataKey function in Installer from @yarnpkg/core has been moved to Linker.

  • renderForm's options argument is now required to enforce that custom streams are always specified.

  • npmConfigUtils.getAuditRegistry no longer takes a Manifest as its first argument.

  • The FetchOptions.skipIntegrityCheck option has been removed. Use FetchOptions.cacheOptions.skipIntegrityCheck instead.

  • MapConfigurationValue has been removed. Use miscUtils.ToMapValue instead.

  • Manifest.isManifestFieldCompatible and Manifest.prototype.isCompatibleWith{OS,CPU} have been removed. Use Manifest.prototype.getConditions and structUtils.isPackageCompatible instead.

  • versionUtils.{fetchBase,fetchRoot,fetchChangedFiles} have been moved from @yarnpkg/plugin-version to @yarnpkg/plugin-git. Use gitUtils.{fetchBase,fetchRoot,fetchChangedFiles} instead.

  • For consistency reasons:

    • Link{Resolver,Fetcher} have been renamed to Portal{Resolver,Fetcher}
    • RawLink{Resolver,Fetcher} have been renamed to Link{Resolver,Fetcher}

  • FakeFS classes are now required to implement lutimes{Sync,Promise}.

  • workspace.dependencies has been removed. Use workspace.anchoredPackage.dependencies instead.

  • The Installer class must now return BuildRequest structures instead of BuildDirective[]. This lets you mark that the build must be skipped, and the reason why.

  • startCacheReport has been removed, and is now part of the output generated by fetchEverything.

  • forgettableNames & forgettableBufferSize have been removed (the only messages using them have been removed, making the forgettable logs implementation obsolete).

  • workspace.locator has been removed. You can instead use:

    • workspace.anchoredLocator to get the locator that's used throughout the dependency tree.
    • workspace.manifest.version to get the workspace version.

  • configuration.{packageExtensions,refreshPackageExtensions} have been removed. Use configuration.getPackageExtensions instead.

  • configuration.normalizePackage now requires a packageExtensions option.

  • ProjectLookup has been removed. Both Configuration.find and Configuration.findProjectCwd now always do a lockfile lookup.

Installs
  • Yarn now caches npm version metadata, leading to faster resolution steps and decreased network data usage.
  • The pnpm linker avoids creating symlinks that lead to loops on the file system, by moving them higher up in the directory structure.
  • The pnpm linker no longer reports duplicate "incompatible virtual" warnings.
Features
  • enableOfflineMode is a new setting that, when set, will instruct Yarn to only use the metadata and archives already stored on the local machine rather than download them from the registry. This can be useful when performing local development under network-constrained environments (trains, planes, ...).
  • yarn run bin now injects the environment variables defined in .env.yarn when spawning a process. This can be configured using the injectEnvironmentFiles variable.
  • yarn workspaces foreach now automatically enables the yarn workspaces foreach ! --verbose flag in interactive terminals.
  • Constraints can now be written in JavaScript. See the revamped documentation for more information.
Bugfixes
  • yarn dlx will no longer report false-positive UNUSED_PACKAGE_EXTENSION warnings
  • yarn workspace will now set $INIT_CWD to the CLI working directory rather than the workspace root.
Shell
  • The builtin shell now supports whitespace-only commands.
Compatibility
  • The patched filesystem now supports FileHandle.readLines.
  • PnP now reports missing files when in watch mode.

v3.8.2

Compare Source

v3.8.1

Compare Source

v3.8.0

Compare Source

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 Renovate Bot.

This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [yarn](https://github.com/yarnpkg/berry) | [`3.7.0` -> `4.2.2`](https://renovatebot.com/diffs/npm/yarn/3.7.0/4.2.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/yarn/4.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/yarn/4.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/yarn/3.7.0/4.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/yarn/3.7.0/4.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>yarnpkg/berry (yarn)</summary> ### [`v4.2.2`](https://github.com/yarnpkg/berry/compare/bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf...effc932614d5351bbfeed8e0e6aa4b2c6c52821d) [Compare Source](https://github.com/yarnpkg/berry/compare/bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf...effc932614d5351bbfeed8e0e6aa4b2c6c52821d) ### [`v4.2.1`](https://github.com/yarnpkg/berry/compare/9a853e35cfe44d1cbd17b9739f68e90d1c79c96e...bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf) [Compare Source](https://github.com/yarnpkg/berry/compare/9a853e35cfe44d1cbd17b9739f68e90d1c79c96e...bf24f592eb0a7e8ac207387b0d60ea2ac7d66ebf) ### [`v4.2.0`](https://github.com/yarnpkg/berry/compare/6b7621f0736ef7ed423672392882d68592d61c81...9a853e35cfe44d1cbd17b9739f68e90d1c79c96e) [Compare Source](https://github.com/yarnpkg/berry/compare/6b7621f0736ef7ed423672392882d68592d61c81...9a853e35cfe44d1cbd17b9739f68e90d1c79c96e) ### [`v4.1.1`](https://github.com/yarnpkg/berry/compare/52909a5e0d2fe72245957870bcd654218d93ef72...6b7621f0736ef7ed423672392882d68592d61c81) [Compare Source](https://github.com/yarnpkg/berry/compare/52909a5e0d2fe72245957870bcd654218d93ef72...6b7621f0736ef7ed423672392882d68592d61c81) ### [`v4.1.0`](https://github.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#410) [Compare Source](https://github.com/yarnpkg/berry/compare/a64075561a6476aa79d0fa1012ecf6b1633a88f2...52909a5e0d2fe72245957870bcd654218d93ef72) - Tweaks `-,--verbose` in `yarn workspaces foreach`; `-v` will now only print the prefixes, `-vv` will be necessary to also print the timings. - Adds a new `--json` option to `yarn run` when called without script name - Fixes `node-modules` linker `link:` dependencies mistreatment as inner workspaces, when they point to a parent folder of a workspace - Fixes spurious "No candidates found" errors - Fixes missing executable permissions when using `nodeLinker: pnpm` - Fixes packages being incorrectly flagged as optional - Fixes cache key corruptions due to uncontrolled git merges - Fixes `yarn version apply --all --dry-run` making unexpected changes - Fixes `yarn npm login` when the remote registry is Verdaccio ### [`v4.0.2`](https://github.com/yarnpkg/berry/compare/be5a1bf87c2de22d8098b3a19a391cc40dfd2f3b...a64075561a6476aa79d0fa1012ecf6b1633a88f2) [Compare Source](https://github.com/yarnpkg/berry/compare/be5a1bf87c2de22d8098b3a19a391cc40dfd2f3b...a64075561a6476aa79d0fa1012ecf6b1633a88f2) ### [`v4.0.1`](https://github.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#401) [Compare Source](https://github.com/yarnpkg/berry/compare/c6764b28f8e8dbdac7ad318d6d98b5d5f0f4679e...be5a1bf87c2de22d8098b3a19a391cc40dfd2f3b) - Fixes creation of symlinks for `node-modules` linker when inner workspace depends on outer workspace - Fixes progress bars when the terminal is too large - Fixes crashes while running Yarn within Docker within GitHub Actions - Fixes `yarn npm audit --ignore NUM` which didn't apply to deprecations - Fixes `yarn npm audit --json` which didn't print the right output format - Fixes an incorrect type export in `@yarnpkg/core` - Implements back the `yarn explain peer-requirements` command ### [`v4.0.0`](https://github.com/yarnpkg/berry/blob/HEAD/CHANGELOG.md#400) [Compare Source](https://github.com/yarnpkg/berry/compare/450097c303ab0247f131291ed6916bffaa42d5f8...c6764b28f8e8dbdac7ad318d6d98b5d5f0f4679e) ##### **Major Changes** - With Node.js 16's [now being End of Life'd](https://nodejs.org/en/blog/announcements/nodejs16-eol), we dropped support for Node.js versions lower than 18.12. - Some important defaults have changed: - `yarn init` and `yarn set version` will prefer using `packageManager` rather than `yarnPath` when possible (when they detect `COREPACK_ROOT` in your environment variables). - `yarn init` will no longer use zero-install by default. You still can enable it, but it should make it easier to start one-of projects without having to rewrite the configuration afterwards. - As a result, `enableGlobalCache` now defaults to `true`. If your project uses Zero-Installs, the first `yarn install` you run after migrating to 4.0 will automatically set `enableGlobalCache: false` in your local `.yarnrc.yml`. - `yarn workspaces foreach` now requires one of `--all`, `--recursive`, `--since`, or `--worktree` to be explicitly specified; the previous default was `--worktree`, but it was rarely what users expected. - `compressionLevel` now defaults to `0` rather than `mixed`. It's been proved significantly faster on installs, and the size impact was reasonable enough to change the default. Note that it benefits you **even if you use Zero-Installs**: as per our tests, a zero-compression is actually easier to handle for Git (you can see by yourself with those examples using [`compressionLevel: 0`](https://github.com/yarnpkg/example-repo-zip0) vs [`compressionLevel: mixed`](https://github.com/yarnpkg/example-repo-zipn)). - To avoid making the upgrade too disruptive, Yarn will check whether Zero-Installs are enabled the first time you run `yarn install` after migrating from 3.6 to 4.0. If you do, it will automatically set the old default (`compressionLevel: mixed`) in your `.yarnrc.yml` file. You can then remove it whenever you feel ready to actually change the compression settings. - All official Yarn plugins are now included by default in the bundle we provide. You no longer need to run `yarn plugin import` for *official* plugins (you still need to do it for third-party plugins, of course). - This doesn't change anything to the plugin API we provide, which will keep being maintained. - Yarn still has a modular architecture and uses the exact same APIs as contrib plugins; all that changes is how we distribute our own features. - Yarn's UI during installs has been greatly improved: - Packages added and removed from the lockfile are now explicitly reported. - Fluctuations in the project cache size are now reported as a single line. - Unactionable warnings (`node-gyp` and transitive peer dependency errors) have been removed. - Skipped builds are now only reported during initial installs and manual `yarn rebuild` calls. - The Yarn version is now displayed on installs to help us investigate issues [when reported as screenshots](https://meta.stackoverflow.com/questions/285551/why-should-i-not-upload-images-of-code-data-errors/285557#285557). - Deprecation checks have been moved to `yarn npm audit`. - Some settings were renamed or removed: - `caFilePath` is now `httpsCaFilePath` - `preferAggregateCacheInfo` has been removed (it's now always on) - `pnpDataPath` has been removed to adhere to our new [PnP specification](https://yarnpkg.com/advanced/pnp-spec). For consistency, all PnP files will now be hardcoded to a single value so that third-party tools can implement the PnP specification without relying on the Yarn configuration. - The `yarn npm audit` command has been reimplemented: - The audit registry must now implement the `/-/npm/v1/security/advisories/bulk` endpoint. - The `npmAuditRegistry` can be used to temporarily route audit queries to the npm registry. - Deprecations are now returned by default. To silence them, use `yarn npm audit ! --no-deprecations`. - Some legacy layers have been sunset: - Plugins cannot access the Clipanion 2 APIs anymore (upgrade to [Clipanion 3](https://github.com/arcanis/clipanion)) - Plugins cannot access the internal copy of Yup anymore (use [Typanion](https://github.com/arcanis/typanion) instead) - Yarn will no longer remove the old Yarn 2.x `.pnp.js` file when migrating. - The `--assume-fresh-project` flag of `yarn init` has been removed. ##### **API Changes** The following changes only affect people writing Yarn plugins: - The `ZipFS` and `ZipOpenFS` classes have been moved from `@yarnpkg/fslib` to `@yarnpkg/libzip`. They no longer need or accept the `libzip` parameter. - Reading the zip archives is now done on the Node.js side for performance; as a result, the `open`, `ZIP_CREATE`, and `ZIP_TRUNCATE` bindings are no longer needed for `ZipFS` and have also been removed. - The `dependencies` field sent returned by `Resolver#resolve` must now be the result of a `Configuration#normalizeDependencyMap` call. This change is prompted by a refactoring of how default protocols (ie `npm:`) are injected into descriptors. The previous implementation caused various descriptors to never be normalized, which made it difficult to know what were the descriptors each function should expect. - Similarly, the descriptors returned by `Resolve#getResolutionDependencies` are now expected to be the result of `Configuration#normalizeDependency` calls. - Note that this only applies to the `dependencies` field; the `peerDependencies` field is unchanged, as it must only contains semver ranges without any protocol (with an exception for `workspace:`, but that's not relevant here). - The `Resolve#getResolutionDependencies` function must now return an object of arbitrary string keys and descriptor values (instead of a map with `DescriptorHash` keys). Those descriptors will be resolved and assigned to the same keys as the initial object. This change allows resolvers to wrap resolution dependencies from other resolvers, which wasn't possible before since it'd have caused the key to change. - The `generateLoader` function in `@yarnpkg/pnp` no longer generates the `$$SETUP_STATE` function, it now needs to be present in the `loader` passed to the function. - The `getCustomDataKey` function in `Installer` from `@yarnpkg/core` has been moved to `Linker`. - `renderForm`'s `options` argument is now required to enforce that custom streams are always specified. - `npmConfigUtils.getAuditRegistry` no longer takes a `Manifest` as its first argument. - The `FetchOptions.skipIntegrityCheck` option has been removed. Use `FetchOptions.cacheOptions.skipIntegrityCheck` instead. - `MapConfigurationValue` has been removed. Use `miscUtils.ToMapValue` instead. - `Manifest.isManifestFieldCompatible` and `Manifest.prototype.isCompatibleWith{OS,CPU}` have been removed. Use `Manifest.prototype.getConditions` and `structUtils.isPackageCompatible` instead. - `versionUtils.{fetchBase,fetchRoot,fetchChangedFiles}` have been moved from `@yarnpkg/plugin-version` to `@yarnpkg/plugin-git`. Use `gitUtils.{fetchBase,fetchRoot,fetchChangedFiles}` instead. - For consistency reasons: - `Link{Resolver,Fetcher}` have been renamed to `Portal{Resolver,Fetcher}` - `RawLink{Resolver,Fetcher}` have been renamed to `Link{Resolver,Fetcher}` - `FakeFS` classes are now required to implement `lutimes{Sync,Promise}`. - `workspace.dependencies` has been removed. Use `workspace.anchoredPackage.dependencies` instead. - The `Installer` class must now return `BuildRequest` structures instead of `BuildDirective[]`. This lets you mark that the build must be skipped, and the reason why. - `startCacheReport` has been removed, and is now part of the output generated by `fetchEverything`. - `forgettableNames` & `forgettableBufferSize` have been removed (the only messages using them have been removed, making the forgettable logs implementation obsolete). - `workspace.locator` has been removed. You can instead use: - `workspace.anchoredLocator` to get the locator that's used throughout the dependency tree. - `workspace.manifest.version` to get the workspace version. - `configuration.{packageExtensions,refreshPackageExtensions}` have been removed. Use `configuration.getPackageExtensions` instead. - `configuration.normalizePackage` now requires a `packageExtensions` option. - `ProjectLookup` has been removed. Both `Configuration.find` and `Configuration.findProjectCwd` now always do a lockfile lookup. ##### Installs - Yarn now caches npm version metadata, leading to faster resolution steps and decreased network data usage. - The `pnpm` linker avoids creating symlinks that lead to loops on the file system, by moving them higher up in the directory structure. - The `pnpm` linker no longer reports duplicate "incompatible virtual" warnings. ##### Features - `enableOfflineMode` is a new setting that, when set, will instruct Yarn to only use the metadata and archives already stored on the local machine rather than download them from the registry. This can be useful when performing local development under network-constrained environments (trains, planes, ...). - `yarn run bin` now injects the environment variables defined in `.env.yarn` when spawning a process. This can be configured using the `injectEnvironmentFiles` variable. - `yarn workspaces foreach` now automatically enables the `yarn workspaces foreach ! --verbose` flag in interactive terminals. - Constraints can now be written in JavaScript. See the [revamped documentation](/features/constraints) for more information. ##### Bugfixes - `yarn dlx` will no longer report false-positive `UNUSED_PACKAGE_EXTENSION` warnings - `yarn workspace` will now set `$INIT_CWD` to the CLI working directory rather than the workspace root. ##### Shell - The builtin shell now supports whitespace-only commands. ##### Compatibility - The patched filesystem now supports `FileHandle.readLines`. - PnP now reports missing files when in watch mode. ### [`v3.8.2`](https://github.com/yarnpkg/berry/compare/4308dca8091438e8f88682e59ef5ba5bc72241ca...450097c303ab0247f131291ed6916bffaa42d5f8) [Compare Source](https://github.com/yarnpkg/berry/compare/4308dca8091438e8f88682e59ef5ba5bc72241ca...450097c303ab0247f131291ed6916bffaa42d5f8) ### [`v3.8.1`](https://github.com/yarnpkg/berry/compare/a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae...4308dca8091438e8f88682e59ef5ba5bc72241ca) [Compare Source](https://github.com/yarnpkg/berry/compare/a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae...4308dca8091438e8f88682e59ef5ba5bc72241ca) ### [`v3.8.0`](https://github.com/yarnpkg/berry/compare/ea39bf05158c791ed51cc924284ac4603be4a5ba...a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae) [Compare Source](https://github.com/yarnpkg/berry/compare/ea39bf05158c791ed51cc924284ac4603be4a5ba...a71d42c2ffd6278a202cccb5fb92c3ac0caf9cae) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi41Ny40IiwidXBkYXRlZEluVmVyIjoiMzYuNTcuNCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciJ9-->
renovate-bot added 1 commit 2023-10-22 20:57:55 +02:00
Some checks failed
ci/woodpecker/push/checks Pipeline failed
Details
83d4a62947 chore(deps): update yarn to v4
renovate-bot scheduled this pull request to auto merge when all checks succeed 2023-10-22 20:57:55 +02:00
renovate-bot commented 2023-10-22 20:57:55 +02:00
Author
Collaborator
Copy link

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

  • Branch has one or more failed status checks
### Branch automerge failure This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead. ___ * Branch has one or more failed status checks
renovate-bot force-pushed renovate/major-yarn-monorepo from 83d4a62947 to 020b3b619d 2023-10-23 03:02:07 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 020b3b619d to 523e211ba7 2023-10-25 13:02:19 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 523e211ba7 to d3cf245167 2023-10-26 11:02:15 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from d3cf245167 to d52a9fdecc 2023-10-27 06:02:05 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from d52a9fdecc to d0c61c4dcc 2023-10-28 13:03:14 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from d0c61c4dcc to 9b76a6ef64 2023-10-28 18:02:22 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 9b76a6ef64 to 3dd5d5e8a6 2023-10-30 02:01:58 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 3dd5d5e8a6 to 1807c34cae 2023-10-31 04:02:13 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 1807c34cae to b51a9eb177 2023-10-31 08:02:05 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from b51a9eb177 to 7a8bb282c1 2023-10-31 11:02:12 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 7a8bb282c1 to ef840d0230 2023-11-03 23:02:41 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from ef840d0230 to 17af09a217 2023-11-04 02:02:38 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 17af09a217 to bee02528d7 2023-11-06 02:02:08 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from bee02528d7 to 6daf70ce8f 2023-11-08 00:02:08 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 6daf70ce8f to b1b3854276 2023-11-10 08:01:44 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from b1b3854276 to fe8775c55a 2023-11-11 10:02:01 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from fe8775c55a to 6c41554f0a 2023-11-11 18:02:27 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 6c41554f0a to aa2b352c24 2023-11-12 07:02:42 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from aa2b352c24 to 4ea75a3d6f 2023-11-12 10:01:54 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 4ea75a3d6f to 1b9e176f9a 2023-11-13 02:02:31 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 1b9e176f9a to b38a5ad2fb 2023-11-13 03:02:36 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from b38a5ad2fb to d7a3520787 2023-11-14 08:01:30 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from d7a3520787 to c6b7a6c9d1 2023-11-14 11:01:12 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from c6b7a6c9d1 to f2365fc650 2023-11-14 21:01:24 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from f2365fc650 to 19c614cf02 2023-11-16 11:02:17 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 19c614cf02 to c26da2575a 2023-11-18 00:02:35 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from c26da2575a to fc670fd84f 2023-11-18 08:02:52 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from fc670fd84f to 053211b220 2023-11-20 02:02:41 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 053211b220 to 84c17d594f 2023-11-21 05:02:20 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 84c17d594f to 9be0a88a43 2023-11-21 23:01:51 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 9be0a88a43 to f155437908 2023-11-24 09:03:45 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from f155437908 to 95bc797210 2023-11-26 16:02:10 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 95bc797210 to c48d92e094 2023-11-27 02:02:47 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from c48d92e094 to e4ebb4274f 2023-11-28 03:01:50 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from e4ebb4274f to b1a0528196 2023-11-30 08:03:18 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from b1a0528196 to 02ec110895 2023-12-02 00:02:57 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 02ec110895 to a9648aaf61 2023-12-02 12:02:55 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from a9648aaf61 to 96fdf468a8 2023-12-03 20:02:30 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 96fdf468a8 to 418c0b907b 2023-12-04 02:02:13 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 418c0b907b to 8346d7ed01 2023-12-08 10:03:13 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 8346d7ed01 to 2b50d552e7 2023-12-11 02:02:40 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 2b50d552e7 to 551ca7f55f 2023-12-11 09:03:10 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 551ca7f55f to 3321c22bce 2023-12-13 12:03:21 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 3321c22bce to d939c37020 2023-12-16 01:02:09 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from d939c37020 to e1b505bfcf 2023-12-17 09:03:04 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from e1b505bfcf to 5004ec5a67 2023-12-18 02:02:52 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from 5004ec5a67 to e186207388 2023-12-25 02:02:26 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from e186207388 to a921a9ac3e 2024-01-30 17:02:53 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from a921a9ac3e to e4d723e34a 2024-03-05 01:03:27 +01:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from e4d723e34a to c0ae37744a 2024-05-02 19:04:23 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from c0ae37744a to ea6e414045 2024-05-02 20:04:28 +02:00 Compare
renovate-bot force-pushed renovate/major-yarn-monorepo from ea6e414045 to adc8d2fc5b 2024-05-08 20:04:36 +02:00 Compare
Some required checks are missing.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/major-yarn-monorepo:renovate/major-yarn-monorepo
git checkout renovate/major-yarn-monorepo
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: saluu/darkness-dependent-vision#7
No description provided.
Delete branch "renovate/major-yarn-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?