-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Comparing changes
Open a pull request
base repository: yarnpkg/berry
base: c6bcbfe8e24c1af6d3b59436c7ef673b367a1335
head repository: yarnpkg/berry
compare: 98c9662047200aec924e34664ba53293474c93bc
- 18 commits
- 48 files changed
- 11 contributors
Commits on May 16, 2023
-
1
Configuration menu - View commit details
-
Copy full SHA for 522d128 - Browse repository at this point
Copy the full SHA 522d128View commit details -
Autocorrects git:// into https:// for GitHub (#5440)
* Autocorrects git:// into https:// * Updates the url
1Configuration menu - View commit details
-
Copy full SHA for 06f1fef - Browse repository at this point
Copy the full SHA 06f1fefView commit details -
1
Configuration menu - View commit details
-
Copy full SHA for 5d3415e - Browse repository at this point
Copy the full SHA 5d3415eView commit details -
fix(plugin-interactive-tools): donβt list folder aliases as outdated β¦
1Configuration menu - View commit details
-
Copy full SHA for 6441c17 - Browse repository at this point
Copy the full SHA 6441c17View commit details -
feat: add --always-auth flag to npm login (#5406)
* feat: add --always-auth flag to npm login * Fixes lint Co-Authored-By: MaΓ«l Nison <nison.mael@gmail.com>
1Configuration menu - View commit details
-
Copy full SHA for fe6420f - Browse repository at this point
Copy the full SHA fe6420fView commit details -
add readme to publishBody (#5374)
* add readme to publishBody * clean test with example * add fallback to project name * cleaning * fix getPublishAccess * cleaning * remove unused parameter * Tweaks * Tweaks tests * Versions * Update publish.test.ts --------- Co-authored-by: MaΓ«l Nison <nison.mael@gmail.com>
1Configuration menu - View commit details
-
Copy full SHA for 3c38006 - Browse repository at this point
Copy the full SHA 3c38006View commit details -
fix(core): correct
.yarnrc.yml
validation error (#5213)* Don't print `[Object object]` as a yarnrc.yml error * Help??? * This seems less than "patch"? It's cosmetic. * Tests
1Configuration menu - View commit details
-
Copy full SHA for edc5455 - Browse repository at this point
Copy the full SHA edc5455View commit details -
docs: explain where the
.yarnrc.yml
should be placed in `migration.β¦β¦md` (#5142) * Update migration.md As someone who has never used yarn before, I had to look this up. * Update migration.md --------- Co-authored-by: MaΓ«l Nison <nison.mael@gmail.com>
1Configuration menu - View commit details
-
Copy full SHA for 707d5b4 - Browse repository at this point
Copy the full SHA 707d5b4View commit details -
docs: add theme colour (#5141)
sanjaiyan: theme color
1Configuration menu - View commit details
-
Copy full SHA for 6f54935 - Browse repository at this point
Copy the full SHA 6f54935View commit details -
1
Configuration menu - View commit details
-
Copy full SHA for 36bf4ef - Browse repository at this point
Copy the full SHA 36bf4efView commit details -
**What's the problem this PR addresses?** <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> ... **How did you fix it?** <!-- A detailed description of your implementation. --> ... **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. --> - [ ] 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` --> - [ ] 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. --> - [ ] I will check that all automated PR checks pass before the PR gets reviewed.
1Configuration menu - View commit details
-
Copy full SHA for 346279e - Browse repository at this point
Copy the full SHA 346279eView commit details -
1
Configuration menu - View commit details
-
Copy full SHA for 80302c3 - Browse repository at this point
Copy the full SHA 80302c3View commit details
Commits on May 17, 2023
-
fix(pnp): esm - handle
parentURL
without afile:
protocol (#5362)**What's the problem this PR addresses?** When chaining Yarn PNP ESM loader with [import-in-the-middle](https://github.com/DataDog/import-in-the-middle) loader, INVALID_URL_SCHEME is thrown because `fileURLToPath()` is run on a parent URL of `node:util?iitm=true` generated by the IITM loader. ``` 2023-03-30T21:40:58.280Z 3364766 U TypeError [ERR_INVALID_URL_SCHEME]: The URL must be of scheme file 2023-03-30T21:40:58.280Z 3364766 U at new NodeError (node:internal/errors:399:5) 2023-03-30T21:40:58.280Z 3364766 U at fileURLToPath (node:internal/url:1212:11) 2023-03-30T21:40:58.280Z 3364766 U at resolve$1 (file:///home/lizf/eve-roster/.pnp.loader.mjs:1993:77) 2023-03-30T21:40:58.280Z 3364766 U at nextResolve (node:internal/modules/esm/hooks:654:28) 2023-03-30T21:40:58.280Z 3364766 U at Hooks.resolve (node:internal/modules/esm/hooks:309:30) 2023-03-30T21:40:58.280Z 3364766 U at ESMLoader.resolve (node:internal/modules/esm/loader:312:26) 2023-03-30T21:40:58.280Z 3364766 U at ESMLoader.getModuleJob (node:internal/modules/esm/loader:172:38) 2023-03-30T21:40:58.281Z 3364766 U at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40) 2023-03-30T21:40:58.281Z 3364766 U at link (node:internal/modules/esm/module_job:75:36) { 2023-03-30T21:40:58.281Z 3364766 U code: 'ERR_INVALID_URL_SCHEME' 2023-03-30T21:40:58.281Z 3364766 U } 2023-03-30T21:40:58.281Z 3364766 U 2023-03-30T21:40:58.281Z 3364766 U Node.js v19.8.1 ``` **How did you fix it?** Ensure fileURLToPath() is only run on file URLs by explicitly checking the URL protocol; if it is not `file`, then default to CWD. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed. --------- Co-authored-by: merceyz <merceyz@users.noreply.github.com>
1Configuration menu - View commit details
-
Copy full SHA for f97880c - Browse repository at this point
Copy the full SHA f97880cView commit details
Commits on May 23, 2023
-
fix(compat): update patch for
typescript@5.1.1-rc
(#5448)**What's the problem this PR addresses?** The PnP compatibility patch for TypeScript doesn't apply to `typescript@5.1.1-rc`. Ref microsoft/TypeScript#35206 **How did you fix it?** Rebased it. **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed.
1Configuration menu - View commit details
-
Copy full SHA for 18f3ee3 - Browse repository at this point
Copy the full SHA 18f3ee3View commit details
Commits on Jun 1, 2023
-
test: fix range for parent URL test (#5463)
**What's the problem this PR addresses?** The test added in #5362 doesn't run on Node.js v17. Fixes https://github.com/yarnpkg/berry/actions/runs/5060283241/jobs/9083017466 **How did you fix it?** Updated the range to match Node.js versions containing nodejs/node#42881 **Checklist** - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). - [x] I have set the packages that need to be released for my changes to be effective. - [x] I will check that all automated PR checks pass before the PR gets reviewed.
1Configuration menu - View commit details
-
Copy full SHA for 1a5e983 - Browse repository at this point
Copy the full SHA 1a5e983View commit details -
Release workflow for stable releases (#5476)
**What's the problem this PR addresses?** I'm currently the only one who can release stable releases. **How did you fix it?** This manual workflow does the same thing I do on my laptop, so it should theoretically work. **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.
1Configuration menu - View commit details
-
Copy full SHA for 4370bff - Browse repository at this point
Copy the full SHA 4370bffView commit details -
Configuration menu - View commit details
-
Copy full SHA for 06b7e08 - Browse repository at this point
Copy the full SHA 06b7e08View commit details -
| Package name | Version | | --- | --- | | `@yarnpkg/cli` | `3.6.0` | | `@yarnpkg/plugin-compat` | `3.1.12` | | `@yarnpkg/plugin-pnp` | `3.2.10` | | `@yarnpkg/pnp` | `3.3.3` | | `@yarnpkg/builder` | `3.3.0` | | `@yarnpkg/core` | `3.5.2` | | `@yarnpkg/plugin-npm-cli` | `3.4.0` | | `@yarnpkg/plugin-interactive-tools` | `3.1.6` | | `@yarnpkg/plugin-git` | `2.6.6` | | `@yarnpkg/plugin-npm` | `2.7.4` |
1Configuration menu - View commit details
-
Copy full SHA for 98c9662 - Browse repository at this point
Copy the full SHA 98c9662View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we canβt render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff c6bcbfe8e24c1af6d3b59436c7ef673b367a1335...98c9662047200aec924e34664ba53293474c93bc