Skip to content
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

Update grunt to version 1.0.1 🚀 #30

Merged
merged 3 commits into from
Apr 7, 2016
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello 👋

🚀🚀🚀

grunt just published its new version 1.0.1, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of grunt – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@teppeis teppeis merged commit 9e767fb into master Apr 7, 2016
@teppeis teppeis deleted the greenkeeper-grunt-1.0.1 branch April 7, 2016 03:42
@ngeor
Copy link

ngeor commented Apr 7, 2016

This is causing problems to us. We are using grunt 0.4.x and grunt-parallelize ^1.1.5.

Some of our grunt plugins are not ready for grunt v1, so we have to use 0.4.
With this PR, you are not supporting 0.4 anymore.

Our temporary workaround is to change our package.json and instead of grunt-parallelize ^1.1.5 we have to use "1.1.5", which prevents us from getting more updates from you.

My recommendation is to:

  • create version 1.1.7 in which you revert the grunt upgrade
  • implement the grunt upgrade, if you have to, in version 1.2.0 or even 2.0.0, to avoid breaking changes.

Best regards,
Nikolaos

@teppeis
Copy link
Owner

teppeis commented Apr 7, 2016

@ngeor Sorry, it's my mistake.
Fixed in v1.1.7.
Thanks!

@ngeor
Copy link

ngeor commented Apr 7, 2016

Thank you so much for a fast response! Tomorrow I'll try to change the version to ^1.1.7 or ~1.1.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants