Published files within a release are immutable.
The time limit is needed because a release can contain different binary wheels for different architectures.
Consider the simplest case: your releases go out via GitHub Actions and separate wheels are built on the Windows, Linux, and macOS runners.
Those won't all end at exactly the same time, so you need a release window during which they can finish and upload their generated files.
That window used to be unlimited, now it's 14 days.
That might seem like a long time, but it means more manual release processes still have time to coordinate, or release processes that need access to less common hardware that might require queuing for a while.
Seems like better setup would be you stage a release and upload but once it’s promoted, its immutable.
loading story #49048049
loading story #49049883
loading story #49050132
{"deleted":true,"id":49049181,"parent":49047864,"time":1784998191,"type":"comment"}
I'd be happier if it was 24 hours by default, with an increased timeout configurable behind 2FA.