| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Adds `approvedGitRepositories` (#7091) ## What's the problem this PR addresses? The `enableScripts` flag doesn't affect `git:` dependencies, which always runs the `pack` script for whatever package manager the project is using. ## How did you fix it? To avoid running arbitrary code through the `git:` protocol we're introducing a new setting called `approvedGitRepositories`. This list of glob will validate the repository urls we clone. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 7 个月前 | |
Implements aggregate peer deps (#5552) **What's the problem this PR addresses?** The "incompatible peer dependencies" warnings are extremely verbose and hard to work with. They can happen when migrating some common packages (for example React), often aren't that important, and take a lot of vertical space (thus desensitizing users to legit warnings). **How did you fix it?** This PR implements a new warning to replace "incompatible peer dependencies": "incompatible peer dependency aggregates". Yes, it's subtle 😄 The message looks like this: ``` node-notifier is listed by your project with version 5.4.0, which doesn't satisfy what @jest/reporters and other dependencies request (^8.0.1 || ^9.0.0 || ^10.0.0). react is listed by your project with version 18.2.0, which doesn't satisfy what react-highlight-words and other dependencies request (but they have non-overlapping ranges!). ``` Note how Yarn is able to join together all the ranges from all the dependencies (or die trying)! I kept the code for the old incompatible peer dependencies, because I'd like to reference them in the output of `yarn explain peer-requirements` (so that the aggregate's explanation would then reference the individual other warnings). I didn't implement the aggregate explanation yet, though, because I suspect it might require rewriting the command, which will have to be a follow-up. **Checklist** <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed. | 3 年前 | |
Adds READMEs (#686) * Adds READMEs * Versions * Fixes infra * Fixes the version tests * Fixes the patch header * Adds a note about the TS logic * Releases the core * Fixes the constraints tests * Don't forget to build plugins for integration tests | 6 年前 | |
Sync master with the changes from master | 3 个月前 |