[Bug]: taskforcesh private repo bullmq not publishing a `time` parameter in their npm metadata

[ben-at-graphite]

Version

5.63.1

Platform

NodeJS

What happened?

Don't think this bug is a function of the package version itself, but rather that the taskforcesh private repo bullmq is not publishing a time parameter in their npm metadata. This causes the following to happen at yarn install:

yarn install
➤ YN0000: · Yarn 4.10.3
➤ YN0000: ┌ Resolution step
➤ YN0082: │ @taskforcesh/bullmq-pro@npm:^7.40.1: No candidates found
➤ YN0000: └ Completed in 0s 683ms
➤ YN0000: · Failed with errors in 0s 688ms

This error message is pretty uninformative, but it happens because npmMinimalAgeGate flags the package as being too new.

See relevant yarn issue, particularly this comment. Workaround was to do:

npmPreapprovedPackages:
- "@taskforcesh/bullmq-pro@7.40.1"
- "bullmq@5.63.1"

How to reproduce.

• Have a .yarnrc.yml with npmMinimalAgeGate: 10080
• Run yarn install on the latest version of BullMQ (5.63.1)

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct