You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the recommended setup, I sometimes get duplicate releases created for the same tag. Perhaps a race condition?
This ends up with some artifacts uploading to one and other artifacts the other, requiring me to delete the releases and re-run the CI. Perhaps there's an atomic way to do the check/creation step?
Note: I thought this was a total fluke the first time it happened, but I've seen it 2 or 3 times now with https://github.com/yaakapp/app (78 releases)
The text was updated successfully, but these errors were encountered:
gschier
changed the title
Duplicate Releases Created
Duplicate Releases Sometimes Created
Sep 17, 2024
I would still love to have some kind of workaround so not everyone needs to switch to multiple jobs but i'm out of (reasonable) ideas.
Note: I thought this was a total fluke the first time it happened, but I've seen it 2 or 3 times now with yaakapp/app (78 releases)
Interesting, you're on first place then. You're also the second person reporting this in the last ~2 weeks. The last report before that was years ago so i wonder if something changed on the server side (cause the action didn't change recently) 🤔
Yes, I wonder if it is indeed a server issue. I don't have any duplicates to look at right now but I do remember looking into it the first time it happened, expecting two platforms to have finished at a similar time, but they were minutes apart (I could be misremembering and will make sure to keep them around to debug, next time)
I also have this issue. Just created two duplicate releases, and it's happened a few times before.
I will add this: the time it just happened I ran the release twice. So it was doing two in parallel. I almost think it can't handle that and you need to do one release at a time...
Using the recommended setup, I sometimes get duplicate releases created for the same tag. Perhaps a race condition?
This ends up with some artifacts uploading to one and other artifacts the other, requiring me to delete the releases and re-run the CI. Perhaps there's an atomic way to do the check/creation step?
Note: I thought this was a total fluke the first time it happened, but I've seen it 2 or 3 times now with https://github.com/yaakapp/app (78 releases)
The text was updated successfully, but these errors were encountered: