News for hackers. Stuff that matters.
Re:PyPI Blog: Releases now reject new files after 14 days by simonw on Saturday July 25, 2026 @10:30AM (#49047864)
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.

Re:PyPI Blog: Releases now reject new files after 14 days by stackskipton on Saturday July 25, 2026 @10:47AM (#49048018)
Seems like better setup would be you stage a release and upload but once it’s promoted, its immutable.
Re:PyPI Blog: Releases now reject new files after 14 days by woodruffw on Saturday July 25, 2026 @10:51AM (#49048049)
Yes, that would be a better setup and it’s exactly what PyPI is moving to[1]. This closes a gap in the legacy upload API, which evolved over time instead of being designed to avoid these kinds of problems.

[1]: https://peps.python.org/pep-0694/

Re:PyPI Blog: Releases now reject new files after 14 days by twosdai on Saturday July 25, 2026 @01:53PM (#49049883)
I agree. I am not sure why they dont "just" wait until all the releases are ready before publishing and give a 14 day "deadline to publish" instead of a potential security vulnerability.

I understand wanting to get things out ASAP. but two weeks is not the end of the world to wait as a consumer of professional software packages.

Re:PyPI Blog: Releases now reject new files after 14 days by crabbone on Saturday July 25, 2026 @02:17PM (#49050132)
There's no reason a public index should allow any "staging" time for releases. It's the whole point of the release: once it's done, it's sealed. Oh, you messed up? -- Either make a new release, or release patches for the old one. Do not use production release server as your testing ground. It's not meant to do that, it makes it unnecessarily complicated. Test whatever you release on your own, outside of production grounds.
Re:PyPI Blog: Releases now reject new files after 14 days by simonw on Saturday July 25, 2026 @05:11PM (#49051610)
That's the direction PyPI is going: https://news.ycombinator.com/item?id=49007291#49047014
Re:PyPI Blog: Releases now reject new files after 14 days by dralley on Saturday July 25, 2026 @10:44AM (#49047995)
I'd be happier if it was 24 hours by default, with an increased timeout configurable behind 2FA.