Skip to content

Commit

Permalink
ci(release): force push release tag (#3380) (#3391)
Browse files Browse the repository at this point in the history
Since we're only pushing a tag, this shouldn't delete commits

Even if someone adds commits in the meantime, we still want to move the
release tag to the commit we have just pushed.

Without this change, we'll see a "rejected stale info" error in CI

(cherry picked from commit da79706)
  • Loading branch information
ev-codes authored Sep 30, 2024
1 parent f109982 commit 9ef552b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/RELEASE.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -250,7 +250,7 @@ jobs:
git commit -am "ci: release version ${RELEASE_VERSION}"
git push --force-with-lease origin ${RELEASE_BRANCH}
git tag -fa ${RELEASE_VERSION} -m "ci: release version ${RELEASE_VERSION}"
git push --force-with-lease origin ${RELEASE_VERSION}
git push --force origin ${RELEASE_VERSION}
env:
RELEASE_VERSION: ${{ github.event.release.tag_name }}
Expand Down

0 comments on commit 9ef552b

Please sign in to comment.