-
Notifications
You must be signed in to change notification settings - Fork 335
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
Fix failing Heroku review app #833
Conversation
Can you add context to this commit that explains why we are pinning it again please? |
fbb3ffe
to
a7fd701
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs commit that explains why we need to pin
And changelog entry until we make a decision on #834
Update 10.5.0 fails with this
and i found this cloudfour/core-gulp-tasks#63 Update to Gulp 4 in firebreak? |
In #827 we removed pinning teh node version, instead specifiying the minimum version. This resulted in Heroku failing as there is an error in the gulp taks in node 10.5.0 Heroku installs. Until we decide to upgrade to Gulp 4 we need to pin the version in package.json. Alternative option is to remove version entirely, although we want to set that for anyone wanting to contribute using `yarn` instead of `npm`.
a7fd701
to
20afba3
Compare
updated with requested changes |
Great work, thanks Jani |
In #827 we removed pinning the node version, instead specifying the minimum version.
This resulted in Heroku failing as there is an error in the gulp taks in node 10.5.0 Heroku installs.
Until we decide to upgrade to Gulp 4 we need to pin the version in package.json.
Alternative option is to remove version entirely, although we want to set that for anyone wanting to contribute using
yarn
instead ofnpm
.Heroku used Node 10.5, built and deployed correctly
When requesting the site it threw a 503 error
Firstly we tried removing the space between number and greaterOrEqual sign, but that didn't work.