Currently, the PyPI release CI is triggered when a GitHub release is created.
However, if the release is created as a draft and published later, the CI is not triggered.
To address this, set the trigger to initiate when the release is published (see GitHub documentation).
Currently, the PyPI release CI is triggered when a GitHub release is created.
However, if the release is created as a draft and published later, the CI is not triggered.
To address this, set the trigger to initiate when the release is published (see GitHub documentation).