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
This commit is contained in:
parent
8dc10556e8
commit
b1aa295923
|
|
@ -94,7 +94,7 @@ echo "==================== Publishing version ${VERSION} ================"
|
||||||
node ./utils/workspace.js --ensure-consistent
|
node ./utils/workspace.js --ensure-consistent
|
||||||
node ./utils/workspace.js --list-public-package-paths | while read package
|
node ./utils/workspace.js --list-public-package-paths | while read package
|
||||||
do
|
do
|
||||||
npm publish ${package} --tag="${NPM_PUBLISH_TAG}"
|
npm publish --access=public ${package} --tag="${NPM_PUBLISH_TAG}"
|
||||||
done
|
done
|
||||||
|
|
||||||
echo "Done."
|
echo "Done."
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue