[Bug?]: npmMinimalAgeGate is defined in minutes, documentation says days are supported

[erlend-skarpnes]

Self-service

• I'd be willing to implement a fix

Describe the bug

When setting up npmMinimalAgeGate, I followed the documentation on https://yarnpkg.com/configuration/yarnrc#npmMinimalAgeGate and set npmMinimalAgeGate: "7d" and tested on a 5 days old update on a package I didn't have. The update was still included in yarn up and yarn upgrade-interactive. When setting the value to 4320 (3 days in minutes) the same update was not included in yarn up or yarn upgrade-interactive.

If the value is supposed to be in minutes, the documentation should be updated.

To reproduce

Set npmMinimalAgeGate to a value defined in days, and check if an update that should be excluded is included. Set npmMinimalAgeGate to the same value defined in minutes, and see if it is then excluded.

Environment

System:
    OS: macOS 26.1
    CPU: (12) arm64 Apple M2 Max
  Binaries:
    Node: 25.1.0
    Yarn: 4.10.3
    npm: 11.6.2

Additional context

No response

[erlend-skarpnes]

Upon further investigation I see that the "days" formatting has been added in a later versions of Yarn, so I'm closing the issue.

[clemyan]

Hmmm... I'd expect that to throw. Welp, probably no way to fix other than to tell people to upgrade