CI: inconsistent release behavior #381

When no release is produced because no release-triggering commits are present, publishing steps currently fails due to lack of artifacts generated. Instead, publishing must be explicitly skipped, ensuring status clarity.

Also, in the context of recent tooling changes, we need to ensure that publish pipeline still works end-to-end (this could be done for dev release, to avoid producing new official versions)