Reported release failure for cloud.google.com/go/storage

[tritone]

I released cloud.google.com/go/storage v1.16.0 yesterday by merging googleapis/google-cloud-go#4332 . I then got an email with a link to the following build, indicating that the release had failed: https://github.com/googleapis/google-cloud-go/actions/runs/980149026

The tag creation appears to have succeeded, and the release is visible on github and pkg.go.dev. I'm wondering if there is anything else that I need to do in response to this failure?

[chingor13]

Your repo has 2 types of releases:

1. submodule release (individual releases for special services like storage)
2. meta-package release (all of the packages)

The release in question was a release PR for (1), but the failure was for the meta-package release. release-please is trying to tag v1.16.0 of the meta-package which is incorrect. This is not a use-case that the release-please-action was expecting to validate (2 separate types of releases).

To fix, I would add if conditions to your workflows to ensure it's only running against the correct types of releases.

[tritone]

@chingor13 thanks for clarifying!

@codyoss I think you own these workflows for google-cloud-go, would you be able to fix this?

[codyoss]

I believe this was fixed a while back with googleapis/google-cloud-go#4537. We now do have some failures due to quota, but that is a different issue, so closing this for now.