solver min-release-age usage on update

[Tsingis]

How is

[solver]
min-release-age = 10

supposed to work when doing poetry update or poetry update --lock or poetry show --outdated in pyproject.toml?

[vincere-mori]

min-release-age is applied whenever Poetry asks a remote index (PyPI or another HTTP repository) for the available versions of a package, so it affects update, update --lock and show --outdated the same way - anything that goes through the solver or the "which versions exist" lookup.

Concretely (Poetry 2.4): the value is a number of days. When it's set, Poetry computes a cutoff of now - min-release-age days and drops any version whose files were uploaded after that cutoff from the candidate list. So with min-release-age = 10:

• poetry update / update --lock: the solver only sees versions that are at least 10 days old, so it upgrades to the newest release older than 10 days and skips anything more recent.
• poetry show --outdated: same filtered view, so the "latest" it reports is the newest version that's ≥ 10 days old - a release published 3 days ago won't show up as an available update.

A few things that tripped me up at first:

• It's based on the upload time the index reports. If a version has no upload-time info, Poetry treats it as old enough and keeps it.
• It only affects HTTP repositories that expose upload times (PyPI, private indexes). Path/git/url dependencies aren't filtered.
• You can exempt specific packages with min-release-age-exclude, or whole sources with min-release-age-exclude-source.
• Run with -vv and you'll see exactly what got skipped - it logs Ignoring <pkg> version(s) due to solver.min-release-age=....