Open zckv opened 1 year ago
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Unfortunately, no update as of yet, still in the backlog.
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?
Still in the backlog
The problem
An error is produced on publish command when the asset is already in the release. This error is on github.py:263, and is not critical. The program still return 0 as a status code.
The error happen because the return code is 422 on POST request on existing asset: https://docs.github.com/en/rest/releases/assets?apiVersion=2022-11-28#list-release-assets
To reproduce, use python-semantic-release/upload-to-gh-release@main or semantic-release publish on a release where the assets are already in the GitHub release. The problem can happen naturally with a commit that doesn't trigger a new version, where "No release will be made, VERSION has already been released!" message is displayed after semantic-release version
Expected behavior
There are two possible behavior, as the conflict isn't yet documented in the documentation nor in the code:
I lean toward the second option. I think that a release should contain only the assets built on the tagged version. And it is easier to do.
Logs
From this job output: https://github.com/zckv/semantic-versioning-example/actions/runs/6394206017/job/17355099525