Restricting "open ended" releases on PyPI?

This new restriction also affects TestPyPI. I had been using it as a nightly “dry run” for end-to-end verification of the trusted publishing process. I think my only option now is to use a unique version every day instead of using “–skip-existing”, wasting space on TestPyPI. The 400 error is raised prior to the check for existing individual files: “400 Uploading new files to releases older than 14 days is not allowed.”

See example failure: Release · Calysto/metakernel@0ceb2f1 · GitHub.

Might we be able to remove the restriction on TestPyPI? If not, is there another way to test trusted publishing end-to-end that I’m not thinking of?

5 Likes