From 69c261c2a8a5c92944348454e4c67231c5293db8 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Mon, 30 May 2022 13:04:20 +0200 Subject: [PATCH] fix(ci): use auth token in dry-run-publish step MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I was assuming that it would not be necessary to include it here, but it seems like it is in order for lerna to be able to check whether the current user has publish access to the packages. (That also seems like a good thing to check in the dry-run step, since we’ve had issues before with adding new packages to which the automation bot did not have access yet.) --- .evergreen.yml | 1 + .evergreen/evergreen.yml.in | 1 + 2 files changed, 2 insertions(+) diff --git a/.evergreen.yml b/.evergreen.yml index 68367c20e..7fdc0db4b 100644 --- a/.evergreen.yml +++ b/.evergreen.yml @@ -5114,6 +5114,7 @@ functions: script: | set -e { + echo "//registry.npmjs.org/:_authToken=${devtoolsbot_npm_token}" > .npmrc export NODE_JS_VERSION=${node_js_version} source .evergreen/setup-env.sh export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true" diff --git a/.evergreen/evergreen.yml.in b/.evergreen/evergreen.yml.in index 37755f7fb..3651c81de 100644 --- a/.evergreen/evergreen.yml.in +++ b/.evergreen/evergreen.yml.in @@ -631,6 +631,7 @@ functions: script: | set -e { + echo "//registry.npmjs.org/:_authToken=${devtoolsbot_npm_token}" > .npmrc export NODE_JS_VERSION=${node_js_version} source .evergreen/setup-env.sh export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true"