Deno 2.6's Minimum Dependency Age Flag Ignores Year and Month Durations

A developer tested the --min-dep-age flag in Deno 2.9.6: days and weeks work, but specifying months or years (P1M, P2Y) silently disables the filter and installs the latest package version. The deno.json key is named minimumDependencyAge, and the check is not applied to an already pinned lockfile.

• P30D and P4W correctly roll packages back to older versions
• P1M, P2Y and P100Y are ignored: latest version installed without warnings
• Config key is minimumDependencyAge, not minDepAge; wrong key silently ignored
• With --min-dep-age=P30D vitest installs 4.1.10 instead of 5.0.1 with no messages