melos-action icon indicating copy to clipboard operation
melos-action copied to clipboard

release-tag.yaml fails when not all packages were updated

Open timcreatedit opened this issue 5 months ago • 4 comments

The tagging workflow fails since it attempts to push tags to the remote that already exist. This happens when for example only one of the packages received a version update, so the created tags for the other packages already exist on the remote.

Example output:

$ melos exec
  └> git tag $MELOS_PACKAGE_NAME-v$MELOS_PACKAGE_VERSION
     └> SUCCESS
To https://github.com/whynotmake-it/figmage
 * [new tag]         figmage-v0.1.0-dev.9 -> figmage-v0.1.0-dev.9
 ! [rejected]        figma_variables_api-v0.1.0-dev.6 -> figma_variables_api-v0.1.0-dev.6 (already exists)
 ! [rejected]        figmage_package_generator-v0.1.0-dev.5 -> figmage_package_generator-v0.1.0-dev.5 (already exists)
error: failed to push some refs to 'https://github.com/whynotmake-it/figmage'
hint: Updates were rejected because the tag already exists in the remote.
Error: Process completed with exit code 1.

It is worth noting that the new tag is pushed correctly, so technically everything works as intended, but the workflow displays as failed.

timcreatedit avatar Sep 25 '24 15:09 timcreatedit