Skip to content

Publishing doesn't work if the same commit is tagged #115

Open
@jni

Description

@jni

See this build based on tag v0.1.0 (which is the same commit as v0.1.0rc0):

https://github.com/napari/midi-app-controller/actions/runs/11807932681

which failed with this error:

Transparency log entry created with index: 148521298
Uploading distributions to https://upload.pypi.org/legacy/
Uploading midi_app_controller-0.1.0rc0-py3-none-any.whl
WARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/        
         File already exists ('midi_app_controller-0.1.0rc0-py3-none-any.whl',  
         with blake2_256 hash                                                   
         '74790178cf5fb97f15cb78ffa23cff1b078699fbfab72284ddf383170b06c913').   
         See https://pypi.org/help/#file-name-reuse for more information.     

I have seen this sort of thing before but I don't remember the fix... I don't see any obviously relevant differences between the napari publish workflow and this one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions