Add grunt-release support #23
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
|
Heh. Don't even know how to release without it, so seemed fitting to merge this first |
|
Yah thats cool. Per Travis, it looks like grunt-release does not play nice with node 0.8. We could always pull 0.8 support. Thoughts @patcon? I usually just update the version by hand, create a tag then run |
|
Totally true that it can be easy, but nice to standardize. So I guess we could either drop 0.8 support or use |
|
WTF was I thinking..? :/ OK, removing 0.8 for now but it's your call. We can see what the grunt-release maintainer says on that linked issue |
desmondmorris
added a commit
that referenced
this pull request
Apr 10, 2014
Add grunt-release support
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.
We have it for the generated scripts, but not for this generator. Makes it dead-easy to release :)