-
-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.8.1 #254
0.8.1 #254
Conversation
@jonschlinkert @doowb any objections? |
Can you get away with just bumping |
@jonschlinkert no because I am trying to release a new commit since 0.8.0 |
Why? Sorry if I'm missing something obvious, but bower.json has nothing to do with npm. publishing a new version on npm won't effect bower in any way (and bower.json won't get published to npm), and bower doesn't look at npm or package.json. Bower only looks at github |
I need that new commit in grunt-assemble so I need a new npm version |
Can you explain this a little more? Which new commit are you referring to? |
I need this commit in a release 0ad46f8 |
That makes more sense now, sorry I didn't notice the other commits. We need to also run verb so the readme is updated (there was another change that added a new helper and will change some of the links). There are also some other PRs that might be able to go into a patch version. I'll take a look at those today and see if we can include any of them. Then since bumping the version is part of what we do when releasing, I can just do it at that time. Thanks for pointing it out though. |
yeah makes more sense now, thanks for the detail.
awesome, thanks @doowb! |
@LaurentGoderre merged and published. You should be able to pull down the latest |
No description provided.