Fix lerna canary publishing; use default --canary versioning with git describe
#2693
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.
fixes #2691
I suspect the root cause is that we have not been using annotated git tags. Lerna uses
git describe
behind the scenes to determine the--canary
version. However,git describe
only return the most recent annotated tag, which in our case was v0.23. I believe Peter originally tried to resolve this usinggit fetch --depth=1 origin +refs/tags/*:refs/tags/*
in the GH workflow.Here are the steps I've taken:
git tag -am v0.32.3 "v0.32.3"
git fetch ...
git tag -am ...
(annotated tag)If the CI passes, I'll merge and check if canary is working successfully.