[INTERNAL] Remove greenkeeper

[RandomByte]

And update package-lock.json which got weird with 000a6fe (EDIT: already done with #48, got removed from this commit)

[codeworrior]

And update package-lock.json which got weird with 000a6fe

That's a question that I anyhow had: isn't there a way to check the package-lock.json for plausibility, either locally or as part of the Travis builds? I always felt uncomfortable when adding that file to a change as the diff usually was too big to understand it.

Maybe something like

  cp package-lock.json package-lock-candidate.json
  git checkout -f package-lock.json 
  npm install
  diff -U 3 package-lock-candidate.json package-lock.json

But maybe I just have to ban npm update from my mental toolkit and everything will be fine.

[RandomByte]

@codeworrior This would make sense as part of the Travis build. I think the odd change in 000a6fe might have been caused by the usage of an older npm version.

But what's the purpose of git checkout -f package-lock.json?

[codeworrior]

Well, that would work only locally before commit. Idea was to revert any local changes, let NPM recalculate the package-lock.json and check if there's anything unexpected in the diff.

[RandomByte]

I created SAP/ui5-tooling#22 to track possible CI enhancements.

[RandomByte]

Also see SAP/ui5-logger#15 (comment)