Update dependency Microsoft.Extensions.Logging.Console to 10.0.5 - autoclosed #8539
dependencyupdates[bot]ci.yml
on: pull_request
Matrix: containers / containers
db-container
/
db-container
51s
windows-installers
/
build
2m 15s
Matrix: build
Matrix: container-test / container-test
Annotations
26 errors and 10 warnings
|
Windows-AzureStorageQueues
Process completed with exit code 1.
|
|
windows-installers / build
Process completed with exit code 1.
|
|
Windows-MSMQ
Process completed with exit code 1.
|
|
Linux-AzureStorageQueues
Process completed with exit code 1.
|
|
Windows-PostgreSQL
Process completed with exit code 1.
|
|
Windows-RabbitMQ
Process completed with exit code 1.
|
|
Linux-Default
Process completed with exit code 1.
|
|
Windows-AzureServiceBus
Process completed with exit code 1.
|
|
Linux-PrimaryRavenAcceptance
Process completed with exit code 1.
|
|
Linux-SqlServer
Process completed with exit code 1.
|
|
Windows-SQS
Process completed with exit code 1.
|
|
Linux-PrimaryRavenPersistence
Process completed with exit code 1.
|
|
Windows-Default
Process completed with exit code 1.
|
|
container-test / asb
Process completed with exit code 1.
|
|
container-test / asb
Process completed with exit code 1.
|
|
container-test / asb
Process completed with exit code 1.
|
|
container-test / asb
Process completed with exit code 1.
|
|
container-test / asb
Login failed with Error: The process '/usr/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.
|
|
container-test / asb
JSON is invalid: Expecting value: line 1 column 1 (char 0)
|
|
Linux-SQS
Process completed with exit code 1.
|
|
Linux-RabbitMQ
Process completed with exit code 1.
|
|
Linux-AzureServiceBus
Process completed with exit code 1.
|
|
Windows-PrimaryRavenPersistence
Process completed with exit code 1.
|
|
Windows-SqlServer
Process completed with exit code 1.
|
|
Windows-PrimaryRavenAcceptance
Process completed with exit code 1.
|
|
Linux-PostgreSQL
Process completed with exit code 1.
|
|
db-container / db-container
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3.7.0, docker/setup-buildx-action@v3.12.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
containers / servicecontrol-monitoring
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.19.2, docker/login-action@v3.7.0, docker/setup-buildx-action@v3.12.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
containers / servicecontrol-audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.19.2, docker/login-action@v3.7.0, docker/setup-buildx-action@v3.12.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
containers / servicecontrol
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6.19.2, docker/login-action@v3.7.0, docker/setup-buildx-action@v3.12.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / mssql
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / rabbit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / asb
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@v2.3.0, docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / sqs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / postgresql
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/login-action@v3.7.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
container-test / asq
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/login@v2.3.0, docker/login-action@v3, docker/login-action@v3.7.0, Particular/setup-azurestorage-action@v2.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=*** environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Particular~ServiceControl~5I1Z8D.dockerbuild
|
92.9 KB |
sha256:b480c13b5410018c13ef4bfc6be2124b091d8dadaf12b0699942201625adcb21
|
|
|
Particular~ServiceControl~KU7AJM.dockerbuild
|
90.6 KB |
sha256:66e3dcc14e8b159eccac3e111e48e8abc4c390d400fb36857eb29845b8105403
|
|
|
Particular~ServiceControl~YLEOCL.dockerbuild
|
89.4 KB |
sha256:b4cda4c45c2fb72877138a4d78471b89669815b44e3966aa1c57526664becc8a
|
|