-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see whatβs changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: yarnpkg/berry
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: ab48d624e2490567be531b4e7c7145c5bc6e55f2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: yarnpkg/berry
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: d2afdfcf8819c449dc9784959ab5beb1389a4b26
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 20 files changed
- 4 contributors
Commits on Aug 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 13d5b30 - Browse repository at this point
Copy the full SHA 13d5b30View commit details
Commits on Aug 10, 2024
-
test: fix custom certification tests on Windows (#6450)
## What's the problem this PR addresses? The integration tests using custom certificates have been failing for quite a while on Windows with the error `RequestError: unsuitable certificate purpose`. ## How did you fix it? This error was caused by the test CA certificate used; it was not configured to be used as a CA when it was generated. The test script that generates the CA certificate has been updated to generate it correctly. I used the same configuration options used by the test suite of the `pem` library that we are using for certificate generation: https://github.com/Dexus/pem/blob/3d71b87cec08a565ce5e73e26dd18f53b9e1fdea/test/pem.spec.js#L856 The problem does not seem to be specific to Windows; I was able to reproduce it locally on macOS as well. I don't yet know why it's passing on CI for Ubuntu and macOS, but not for Windows. Perhaps some difference in the images, like the OpenSSL version (they should all be using OpenSSL v1.1.1, but I've seen reports of Windows having v3 installed as well). ## 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.
Configuration menu - View commit details
-
Copy full SHA for 7495114 - Browse repository at this point
Copy the full SHA 7495114View commit details
Commits on Aug 11, 2024
-
feat(nm): Add support for user-defined <workspace>/node_modules symliβ¦
β¦nks (#6416) ## What's the problem this PR addresses? <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> Fixes: #6415 ## How did you fix it? <!-- A detailed description of your implementation. --> Now the `node-modules` linker do not try to delete or recreate `<any_workspace>/node_modules` directories if they are symlinks and the underlying dependencies were removed or newly added. ## 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.
Configuration menu - View commit details
-
Copy full SHA for 7fab4f1 - Browse repository at this point
Copy the full SHA 7fab4f1View commit details
Commits on Aug 24, 2024
-
fix(compat): update patch for
typescript@5.6.1-rc
(#6461)**What's the problem this PR addresses?** The PnP compatibility patch for TypeScript doesn't apply to `typescript@5.6.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.
Configuration menu - View commit details
-
Copy full SHA for 80cb95e - Browse repository at this point
Copy the full SHA 80cb95eView commit details -
| Package name | Version | | --- | --- | | `@yarnpkg/cli` | `4.4.1` | | `@yarnpkg/plugin-compat` | `4.0.8` | | `@yarnpkg/plugin-nm` | `4.0.3` |
Configuration menu - View commit details
-
Copy full SHA for d2afdfc - Browse repository at this point
Copy the full SHA d2afdfcView commit details
There are no files selected for viewing