fix(publish): Fetch tags from origin before creating GitHub release #3788
+1
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A few publishes have failed in cases where "tag exists locally but not on remote", if another fetch is performed it should update local->remote tag references. The push should handle this already but it can't hurt to have it explicitly update right? I also thought that it could be a timing issue or a problem with the `gh` command itself (if it uses some other method to check remote tags). If I'm completely wrong, apologies for wasting your time.
github-actions
bot
force-pushed
the
dev
branch
from
772b621 to
eb855e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few publishes have failed in cases where "tag exists locally but not on remote", if another fetch is performed it should update local->remote tag references. The push should handle this already but it can't hurt to have it explicitly update right?
I also thought that it could be a timing issue or a problem with the
ghcommand itself (if it uses some other method to check remote tags).If I'm completely wrong, apologies for wasting your time.