matrei commented on PR #15623: URL: https://github.com/apache/grails-core/pull/15623#issuecomment-4607081918
> @jamesfredley we 100% had it kick off with no changes other than creating the release. Remove the concurrency and create a release to see it, but this was a constant problem in our release process that I would have to immediately kill the job after push. I'm not sure why it was doing this, but nothing had actually committed other than the tag. Both @matrei & I saw this across multiple of our repos until we added the concurrency restriction. I know there was a problem that there was another GitHub Release created, I think with the same name, and the release workflow uploaded artifacts to that wrong GitHub Release. I started disabling the the release drafter workflow when doing releases to workaround that issue. I think we should try these changes out. Lets see what happens. I mean, look at the releases page today: https://github.com/apache/grails-core/releases -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
