Repository navigation
devops: move npm publishing to ESRP pipeline (#42171) #8496
Annotations
6 errors and 14 warnings
|
macos-latest - chrome
Process completed with exit code 1.
|
|
macos-latest - chrome
Login failed with Error: The process '/opt/homebrew/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
|
|
macos-latest - chrome
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
|
|
macos-latest - chrome
HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /***/v2.0/.well-known/openid-configuration (Caused by NameResolutionError("HTTPSConnection(host='login.microsoftonline.com', port=443): Failed to resolve 'login.microsoftonline.com' ([Errno 8] nodename nor servname provided, or not known)"))
Traceback (most recent call last):
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connection.py", line 204, in _new_conn
sock = connection.create_connection(
(self._dns_host, self.port),
...<2 lines>...
socket_options=self.socket_options,
)
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/util/connection.py", line 60, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/[email protected]/3.14.6/Frameworks/Python.framework/Versions/3.14/lib/python3.14/socket.py", line 987, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno 8] nodename nor servname provided, or not known
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 788, in urlopen
response = self._make_request(
conn,
...<10 lines>...
**response_kw,
)
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 488, in _make_request
raise new_e
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 464, in _make_request
self._validate_conn(conn)
~~~~~~~~~~~~~~~~~~~^^^^^^
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 1106, in _validate_conn
conn.connect()
~~~~~~~~~~~~^^
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connection.py", line 759, in connect
self.sock = sock = self._new_conn()
~~~~~~~~~~~~~~^^
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connection.py", line 211, in _new_conn
raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: HTTPSConnection(host='login.microsoftonline.com', port=443): Failed to resolve 'login.microsoftonline.com' ([Errno 8] nodename nor servname provided, or not known)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/requests/adapters.py", line 645, in send
resp = conn.urlopen(
method=request.method,
...<9 lines>...
chunked=chunked,
)
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 872, in urlopen
return self.urlopen(
~~~~~~~~~~~~^
method,
^^^^^^^
...<13 lines>...
**response_kw,
^^^^^^^^^^^^^^
)
^
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/connectionpool.py", line 842, in urlopen
retries = retries.increment(
method, url, error=new_e, _pool=self, _stacktrace=sys.exc_info()[2]
)
File "/opt/homebrew/Cellar/azure-cli/2.88.0/libexec/lib/python3.14/site-packages/urllib3/util/retry.py", line 543, in increment
raise MaxRetryError(_pool, url, reason) from reason # type: ignore[arg-type]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /***/v2.0/.well-known/openid-configuration (Caus
|
|
macos-latest - chrome
The command failed with an unexpected error. Here is the traceback:
|
|
windows-latest - firefox
Process completed with exit code 1.
|
|
ubuntu-latest - chrome
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-latest - chromium
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos-latest - webkit
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos-latest - chrome
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos-latest - chrome
Login cleanup failed with Error: The process '/opt/homebrew/bin/az' failed with exit code 1. Cleanup will be skipped.
|
|
macos-latest - chromium
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-latest - webkit
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos-latest - firefox
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest - webkit
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-latest - firefox
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest - chromium
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest - msedge
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest - chrome
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest - firefox
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|