ci(release.yml): fetch tags to fix canaryExists logic #66
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.
Previously, tags weren't actually fetched, throwing off the
canaryExists
logic.Interestingly, tags still won't be fetched when
fetch-depth
is > 0 (as is the default, being 1), even when togglingfetch-tags: true
on the checkout action. (See actions/checkout#701).Therefore, I just add a
git fetch --prune --unshallow --tags
to start the step. (Prefer not to setfetch-depth
to 0 and thus fetch all git history.)Depends on #64 (will convert from Draft once merged)