|
Ran
|
Files
50
|
Run time
9s
|
Badge
README BADGES
|
push
github
chore(deps): update pnpm to v10.19.0 (#3015) This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [pnpm](https://pnpm.io) ([source](https://redirect.github.com/pnpm/pnpm/tree/HEAD/pnpm)) | [`10.18.3+sha512.bbd16e6d7a908328f792831b009aadfb08d` -> `10.19.0`](https://renovatebot.com/diffs/npm/pnpm/10.18.3/10.19.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>pnpm/pnpm (pnpm)</summary> ### [`v10.19.0`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#10190) [Compare Source](https://redirect.github.com/pnpm/pnpm/compare/v10.18.3...v10.19.0) ##### Minor Changes - You can now allow specific versions of dependencies to run postinstall scripts. `onlyBuiltDependencies` now accepts package names with lists of trusted versions. For example: ```yaml onlyBuiltDependencies: - nx@21.6.4 || 21.6.5 - esbuild@0.25.1 ``` Related PR: [#​10104](https://redirect.github.com/pnpm/pnpm/pull/10104). - Added support for exact versions in `minimumReleaseAgeExclude` [#​9985](https://redirect.github.com/pnpm/pnpm/issues/9985). You can now list one or more specific versions that pnpm should allow to install, even if those versions donโt satisfy the maturity requirement set by `minimumReleaseAge`. For example: ```yaml minimumReleaseAge: 1440 minimumReleaseAgeExclude: - nx@21.6.5 - webpack@4.47.0 || 5.102.1 ``` </details> --- ### Configuration ๐ **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). ๐ฆ **Automerge**: Disabled by config. ... (continued)
1150 of 1190 branches covered (96.64%)
4157 of 4157 relevant lines covered (100.0%)
42.19 hits per line
| Coverage | โ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|