A new release is created if name is omited
vgcpge opened this issue · comments
README states:
When the release info keys (such as name, body, draft, prerelease, etc.) are not explicitly set and there is already an existing release for the tag, the release will retain its original info.
name
is documented as explicitly optional for release update. However, if a release is created using tag_name
and a different name
, and then an update to release is done using tag_name
, while omitting name
, a new release is created instead of the intended update.
The documentation implies that tag_name is the primary key that distinguishes releases, but the actual action uses name as a primary key.
I'm not sure what is the intended behavior here, but the documentation should probably be consistent with actual behavior.
Example of the update behavior:
Release creation: https://github.com/vgcpge/eclipse.copilot/actions/runs/5214840618/jobs/9411641411 (Create Github release section)
An attempt to update the release by uploading an artifact: https://github.com/vgcpge/eclipse.copilot/actions/runs/5214840618/jobs/9411660424 (Upload release artifact section)