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.
This is relevant only for yarn that do not override.
I looked at #95, problem is that yarn try to use the version in package.json to avoid rebuilding, otherwise trowing noisy warnings or possibly errors.
I think proper solution would require to keep version in package.json to the git version, but it's too much complexity for little gain.
Removing the version altogether do not seems to be an option, given build tools expect to find something (even just for ignoring it).
Unsure of the way out, recent way seems better that old / non existing, unsure if we want to bump manually or automate.
I think merging + tagging would work.