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
We recently had two PRs merge and the same time. The one that merged first, ended up tagging the commit of the 2nd. Then the 2nd cancelled itself because the commit was already tagged.
In the release_github job, it has this step to make the tag:
The problem, I think, is that GITHUB_REF: ${{ github.ref }} should be GITHUB_REF: ${{ github.sha }}. The ref changed during the release, so it ended up tagging the wrong commit.
The text was updated successfully, but these errors were encountered:
polothy
added a commit
to polothy/projen
that referenced
this issue
May 16, 2024
…ommits are released at the same time (race condition) (#3584)
The problem, I think, is that `GITHUB_REF: ${{ github.ref }}` should be `GITHUB_REF: ${{ github.sha }}`. The ref changed during the release, so it ended up tagging the wrong commit.
Fixes#3583
---
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
We recently had two PRs merge and the same time. The one that merged first, ended up tagging the commit of the 2nd. Then the 2nd cancelled itself because the commit was already tagged.
In the
release_github
job, it has this step to make the tag:The problem, I think, is that
GITHUB_REF: ${{ github.ref }}
should beGITHUB_REF: ${{ github.sha }}
. The ref changed during the release, so it ended up tagging the wrong commit.The text was updated successfully, but these errors were encountered: