From b1aa2959237f5e6b5194569496a9903bd8af4c39 Mon Sep 17 00:00:00 2001
From: Andrey Lushnikov <aslushnikov@gmail.com>
Date: Thu, 9 Jun 2022 07:22:05 -0700
Subject: [PATCH] devops: fix canary publishing (#14746)

The first time a scoped package is published, it is considered to be
private.

See https://stackoverflow.com/a/44862841/314883
---
 utils/publish_all_packages.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/publish_all_packages.sh b/utils/publish_all_packages.sh
index 8d61d0f451..12cf733495 100755
--- a/utils/publish_all_packages.sh
+++ b/utils/publish_all_packages.sh
@@ -94,7 +94,7 @@ echo "==================== Publishing version ${VERSION} ================"
 node ./utils/workspace.js --ensure-consistent
 node ./utils/workspace.js --list-public-package-paths | while read package
 do
-  npm publish ${package} --tag="${NPM_PUBLISH_TAG}"
+  npm publish --access=public ${package} --tag="${NPM_PUBLISH_TAG}"
 done
 
 echo "Done."