From 78b1dad2a92ef8dd2ed1262ec05348b61da3de9a Mon Sep 17 00:00:00 2001 From: Jonas Jenwald Date: Fri, 20 Mar 2020 15:45:15 +0100 Subject: [PATCH] Don't let Travis run `npm update` during setup Letting Travis update npm packages can lead to unexpected and completely unrelated failures for any PR and/or merge, see e.g. 11719, if there's ever backwards *incompatible* changes when a package is updated. The *exact* package versions are specified in `package-lock.json`, and they should thus be used when running tests. Note that the bots won't update npm packages, and neither should Travis as far as I'm concerned. --- .travis.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 0c0c23f89..60084ff9a 100644 --- a/.travis.yml +++ b/.travis.yml @@ -8,4 +8,3 @@ install: - npm install -g npm@latest - npm install -g gulp-cli - npm install - - npm update