|
Ran
|
Jobs
6
|
Files
51
|
Run time
1min
|
Badge
README BADGES
|
push
github
chore(deps): update pnpm to v11.6.0 (#3475) 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/pnpm)) | [`11.5.3+sha512.7ac1c9193ee8c4782de29bbb48f2a4969ed` → `11.6.0`](https://renovatebot.com/diffs/npm/pnpm/11.5.3/11.6.0) |  |  | --- ### Release Notes <details> <summary>pnpm/pnpm (pnpm)</summary> ### [`v11.6.0`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#1160) [Compare Source](https://redirect.github.com/pnpm/pnpm/compare/v11.5.3...v11.6.0) ##### Minor Changes - `pnpm install` completes without re-resolving when `pnpm-lock.yaml` was deleted but `node_modules` is intact: the up-to-date check now treats the current lockfile (`node_modules/.pnpm/lock.yaml`) — the record of what the previous install materialized — as the wanted lockfile, verifies the manifests still match it, restores `pnpm-lock.yaml` from it, and reports "Already up to date". Previously this scenario triggered a full resolution and a re-verification of every locked package against the registry. - [`615c669`](https://redirect.github.com/pnpm/pnpm/commit/615c669): Added support for configuring URL-scoped registry settings through `npm_config_//…` and `pnpm_config_//…` environment variables, for example: ```text npm_config_//registry.npmjs.org/:_authToken=<token> pnpm_config_//registry.npmjs.org/:_authToken=<token> ``` This provides a file-free way to supply registry authentication. Because the registry a value applies to is encoded in the (trusted) environm... (continued)
1021 of 1065 branches covered (95.87%)
1486 of 1486 relevant lines covered (100.0%)
432.78 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | run-24.x - 27816462910.1 | 51 |
100.0 |
GitHub Action Run | |
| 2 | run-24.0.0 - 27816462910.2 | 51 |
100.0 |
GitHub Action Run | |
| 3 | run-22.19.0 - 27816462910.3 | 51 |
100.0 |
GitHub Action Run | |
| 4 | run-26.x - 27816462910.4 | 51 |
100.0 |
GitHub Action Run | |
| 5 | run-26.0.0 - 27816462910.5 | 51 |
100.0 |
GitHub Action Run | |
| 6 | run-22.x - 27816462910.6 | 51 |
100.0 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|