|
Ran
|
Jobs
6
|
Files
50
|
Run time
1min
|
Badge
README BADGES
|
push
github
chore(deps): update pnpm to v11.20.0 (#3618) This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pnpm](https://pnpm.io) ([source](https://redirect.github.com/pnpm/pnpm/tree/HEAD/pnpm11/pnpm)) | [`11.19.0+sha512.7881f3ed5dcc88cbca4e1c65befa1b22dce` → `11.20.0`](https://renovatebot.com/diffs/npm/pnpm/11.19.0/11.20.0) |  |  | --- ### Release Notes <details> <summary>pnpm/pnpm (pnpm)</summary> ### [`v11.20.0`](https://redirect.github.com/pnpm/pnpm/releases/tag/v11.20.0): pnpm 11.20 [Compare Source](https://redirect.github.com/pnpm/pnpm/compare/v11.19.0...v11.20.0) #### Minor Changes - **Security fix.** Affects projects using `namedRegistries` on pnpm 11.1.0–11.19.x. It is **semi-breaking** for those projects — see "If you use named registries" below. The lockfile recorded no marker for which registry a package came from. Packages were keyed by `name@version` alone, and entry lookup went through `refToRelative(ref, name)`, so a dependency you declared against one registry could be satisfied by an entry that was actually resolved from another. When two registries served the same name and version, both collapsed onto a single `packages:` entry and whichever resolved first decided the tarball every consumer got. That is a package-substitution risk: a package you expect from your private registry could be installed from a different registry that publishes the same name and version, and the lockfile recorded nothing that would let you tell. Packages resolved from a named registry are now recorded under registry-qualified keys (`<name>@<r... (continued)
1056 of 1108 branches covered (95.31%)
1522 of 1522 relevant lines covered (100.0%)
578.37 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | run-26.0.0 - 31399439639.1 | 50 |
100.0 |
GitHub Action Run | |
| 2 | run-26.x - 31399439639.2 | 50 |
100.0 |
GitHub Action Run | |
| 3 | run-22.19.0 - 31399439639.3 | 50 |
100.0 |
GitHub Action Run | |
| 4 | run-24.11.0 - 31399439639.4 | 50 |
100.0 |
GitHub Action Run | |
| 5 | run-24.x - 31399439639.5 | 50 |
100.0 |
GitHub Action Run | |
| 6 | run-22.x - 31399439639.6 | 50 |
100.0 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|