Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 76596c5 head repository: yarnpkg/berryFailed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2b26e3dImprove pnp loader speed and memory: jszip implementation (#6688)
## What's the problem this PR addresses? rework of #6671 TODO: - [ ] check security? - [x] tests - [ ] elaborate mixed compression logic - [ ] benchmarks? - [ ] hide exports and interfaces for external consumers? <!-- 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. --> - [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` --> - [ ] 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. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com>Configuration menu Browse the repository at this point in the history
Adds support for the jsr: protocol (#6752)
## What's the problem this PR addresses? I noticed pnpm/pnpm#9358 and figured it'd make sense to support this in Yarn as well. ## How did you fix it? Yarn will natively understand the `jsr` protocol and automatically reroute the dependency to its `@jsr`-prefixed variant. Still need to add tests. ## 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. --------- Co-authored-by: Luca Casonato <hello@lcas.dev>Configuration menu Browse the repository at this point in the history
ci: properly mint a provenance token in release workflows (#6754)
## What's the problem this PR addresses? Follow-up #6750: enable provenance statements for Yarn ## How did you fix it? <!-- A detailed description of your implementation. --> Added `permissions: id-token: write` to publication workflows ## 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 Browse the repository at this point in the history
Add support for yarn add jsr:@foo/bar (#6757)
## What's the problem this PR addresses? My PR at #6752 added support for the `jsr:` protocol, but in a way that didn't allow for running `yarn add jsr:@foo/bar` (or even `yarn add @foo/bar@jsr:1.0.0`), because it was setup as a conversion pass in dependency maps - ie it didn't integrate well with `suggestUtils`. ## How did you fix it? I refactored the code to now use a proper resolver & fetcher. A hack remains (see description of `getResolutionDependencies`); it's a medium-term solution. I have a better fix in mind, but that will require some refactoring of our internals so it'll be deferred until the next major. ## 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 Browse the repository at this point in the history
test(acceptance-tests): add tests for provenance (#6755)
## What's the problem this PR addresses? <!-- Describe the rationale of your PR. --> <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) --> Follow-up #6750: add tests ## How did you fix it? <!-- A detailed description of your implementation. --> New npm publish acceptance tests that verifies the provenance statement validity ## 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. --------- Co-authored-by: Maël Nison <nison.mael@gmail.com>Configuration menu Browse the repository at this point in the history
| Package name | Version | | --- | --- | | `@yarnpkg/cli` | `4.9.0` | | `@yarnpkg/libzip` | `3.2.0` | | `@yarnpkg/plugin-pnp` | `4.1.0` | | `@yarnpkg/pnp` | `4.1.0` | | `@yarnpkg/core` | `4.4.0` | | `@yarnpkg/plugin-essentials` | `4.4.0` | | `@yarnpkg/plugin-jsr` | `1.1.0` | | `@yarnpkg/plugin-npm` | `3.1.0` | | `@yarnpkg/plugin-npm-cli` | `4.1.0` |Configuration menu Browse the repository at this point in the history
Loading
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 76596c5...2b26e3d
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4