Permalink
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.
...
- 4 commits
- 21 files changed
- 3 contributors
Commits on Sep 18, 2025
-
-
Bust the metadata cache (#6908)
## What's the problem this PR addresses? Our cache key includes all fields from the package metadata ... but the time field isn't part of the package metadata, it's a separate field. As a result the time field is empty for people who already have a hot metadata cache. ## How did you fix it? Manually added the time key. ## 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.
-
fix: support registries without publish times using
minimalAgeGate(#……6907) ## What's the problem this PR addresses? When using registries that don't expose the publish time along with `minimalAgeGate` setting will result in an error of `No candidates found` as the filter will silently fail and simply exclude it without first checking if it's excepted. Closes #6906 ## How did you fix it? To address this I changed types to optional and mark candidates without publish time as automatically needing quarantine when `minimalAgeGate` is set instead of silently failing. ## 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 <[email protected]>
-
| Package name | Version | | --- | --- | | `@yarnpkg/cli` | `4.10.2` | | `@yarnpkg/plugin-npm` | `3.3.1` |
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 @yarnpkg/cli/4.10.1...@yarnpkg/cli/4.10.2