When a cache wheel server is passed via --cache-wheel-server-url, Fromager creates a PyPIProvider for it and applies the package cooldown. If the server supports upload_time, cooldown is enforced. Otherwise, it logs warnings:
release-age cooldown cannot be enforced — upload timestamp support is not yet implemented for PyPI resolver (searching at <CACHE_WHEEL_SERVER_URL>); cooldown check skipped
This produces hundreds of warnings per run, obscuring real errors.
Why cooldown is wrong here
The cache wheel server only contains wheels that fromager itself previously built and uploaded. The cooldown check was already enforced during the original sdist resolution against the upstream source. Re-checking cooldown on wheels we built ourselves is semantically incorrect. The upload timestamp on the cache reflects when our build uploaded it, not when the package was published upstream.
The same logic applies to the local wheel server.
When a cache wheel server is passed via --cache-wheel-server-url, Fromager creates a PyPIProvider for it and applies the package cooldown. If the server supports upload_time, cooldown is enforced. Otherwise, it logs warnings:
This produces hundreds of warnings per run, obscuring real errors.
Why cooldown is wrong here
The cache wheel server only contains wheels that fromager itself previously built and uploaded. The cooldown check was already enforced during the original sdist resolution against the upstream source. Re-checking cooldown on wheels we built ourselves is semantically incorrect. The upload timestamp on the cache reflects when our build uploaded it, not when the package was published upstream.
The same logic applies to the local wheel server.