Conversation
Contributor
Author
|
Do we increase contract / package versions to 0.6.0, right? |
Contributor
I only bump this when we do a release. It stays 0.5.0 until the next tag. Not sure if that is "proper' but that is how I've been doing it with the scripts and lets us pick the version number right before tagging. I would call a v0.6.0-alpha1 once we got the cw20-ics20 contract merged. I want some real world tests on that and a bit more cleanup before v0.6.0 |
ethanfrey
approved these changes
Mar 10, 2021
Contributor
ethanfrey
left a comment
ethanfrey
left a comment
There was a problem hiding this comment.
Looks like a very comprehensive rename. Thanks for taking care of this.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #242.