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
The problem is, gulp 4 has a few major breaking changes compared to gulp 3, so almost every v3 gulpfile needs to be rewritten to support the new gulp 4 syntax.
Is this something that greenkeeper should restrict (i.e. only ever upgrade gulp 3 to higher gulp 3 versions, same with gulp 4), or are greenkeeper users expected to fix all CI build failures before merging the greenkeeper pull requests?
The text was updated successfully, but these errors were encountered:
@GregTheGreek, I haven't heard anything from the greenkeeper team, and I gave up using greenkeeper because I found it to be more effort than it was worth for me. So, no?
Greenkeeper tried to upgrade gulp 3 to gulp 4 in one of my projects (https://github.com/TwitchBronBron/MessageManager/pull/1/files#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R21).
The problem is, gulp 4 has a few major breaking changes compared to gulp 3, so almost every v3 gulpfile needs to be rewritten to support the new gulp 4 syntax.
Is this something that greenkeeper should restrict (i.e. only ever upgrade gulp 3 to higher gulp 3 versions, same with gulp 4), or are greenkeeper users expected to fix all CI build failures before merging the greenkeeper pull requests?
The text was updated successfully, but these errors were encountered: