npm-check-updates 22.2.2 → 22.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -506,6 +506,16 @@ You can also provide a custom function in your .ncurc.js file or when importing
506
506
  cooldown: packageName => (packageName.startsWith('@my-company') ? 0 : 3)
507
507
  ```
508
508
 
509
+ ### Package Manager Configurations
510
+
511
+ If `--cooldown` is not set explicitly, `ncu` automatically reads the cooldown configuration from your package manager's config file:
512
+
513
+ <table>
514
+ <tr><td>npm</td><td>Reads `min-release-age` from `.npmrc`.</td></tr>
515
+ <tr><td>yarn</td><td>Reads `npmMinimalAgeGate` from `.yarnrc.yml`, excluding packages matched by `npmPreapprovedPackages`.</td></tr>
516
+ <tr><td>pnpm</td><td>Reads `minimumReleaseAge` from `pnpm-workspace.yaml`, excluding packages matched by `minimumReleaseAgeExclude`.</td></tr>
517
+ </table>
518
+
509
519
  ### Cooldown Formatting
510
520
 
511
521
  When using `--format cooldown` alongside the `--cooldown` option, `ncu` will show a list of packages that were skipped due to the `--cooldown` threshold.