Increment version to v0.3.2 reflect changes since v0.3.1 #16
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
|
@robertomoutinho Just checking in on this. I can get the latest by pulling from master, but there are still issues caused by folks using Berkshelf since there are differences between your v0.3.1 tag and your master branch (which shows 0.3.1 in metadata.rb but is different from the v0.3.1 tag). You can resolve this by merging my PR. Just trying to help! Thanks! |
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.
@robertomoutinho Can you please merge this pull request to increment the cookbook version? I want to use this cookbook but the v0.3.1 tag doesn't match what's in master. This PR increments the version. If you can also add a tag for this version, I would much appreciate, thanks!