Skip to content

Publish not transactional - doesn't undo release on HTTP error #385

@rogerbinns

Description

@rogerbinns

For a github actions run all the binaries uploaded, but the source failed for no specified reason.

Uploading apsw-sqlite3mc-3.51.0.0.tar.gz
WARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/          
         Bad Request  

But the resulting release is now showing up as current with all the files except that failed source upload.

I would expect this to be transactional - ie the whole thing succeeds, or the whole thing fails.

Even if that isn't the case, I wouldn't expect the release to show up as current.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions