Use MinVer to infer package versions #71
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR uses MinVer to compute assembly versions based on tags in the git history.
I've included a
v0.0.0-rc1tag in here; I intend to squash merge to remove that from the history and then re-add it on the squashed commitThere's a
v0.0.1-rc1at large, which is on thecosmosbranch; will do the same squash merge and then apply on master dance when we merge that.... I needed to push it with
git push origin v0.0.0-rc1for MinVer to pick it up though... but it seems to have been cached and hence not picked up. Merging to see if it gets picked up by next PR