You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make a proper Github release and make sure tagging, nuget, npm, bower, and everything else works. They sometimes fail, but even when that's fixed the release history in Github is boring.
* Add relevant npm keywords and filter out the files that people
actually care about when downloading from npm.
* Stopped using `v` in front of version number.
* Removed dead config for grunt-cdnify.
* Publish to npm with `grunt-npm` and create a Github release with
`grunt-conventional-github-releaser`.
Closes#42
Issue
Make a proper Github release and make sure tagging, nuget, npm, bower, and everything else works. They sometimes fail, but even when that's fixed the release history in Github is boring.
Possible solution
grunt-github-releaser and gh-release both look interesting. We're currently using grunt-bump.
Expected result
Access to
![screenshot 2015-10-03 14 22 56](https://cloud.githubusercontent.com/assets/693684/10262874/4b39e9a2-69da-11e5-9743-af036f11aa45.png)
dry-run
for a test run and the Github should look like this.The text was updated successfully, but these errors were encountered: