Skip to content
CI

Fix/wrong target type after renaming in csolution yaml file #95

Sign in to view logs

Fix/wrong target type after renaming in csolution yaml file

Fix/wrong target type after renaming in csolution yaml file #95

Triggered via pull request March 12, 2026 08:42
@arneschmidarneschmid
synchronize #49
fix/wrong-target-type-after-renaming-in-csolution-yaml-file
Status Failure
Total duration 10m 37s
Artifacts 8

ci.yml

on: pull_request
Build
5m 22s
Build
Matrix: test
Publish release
0s
Publish release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
Test (win32-x64)
Process completed with exit code 1.
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4, step-security/harden-runner@20cf305ff2072d973412fa9b1e3a4f227bda3c76. 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=true 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=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (darwin-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@95d9a5deda9de15063e7595e9719c11c38c90ae2. 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=true 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=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (linux-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: qltysh/qlty-action/coverage@a19242102d17e497f437d7466aa01b528537e899, step-security/harden-runner@95d9a5deda9de15063e7595e9719c11c38c90ae2. 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=true 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=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (win32-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@95d9a5deda9de15063e7595e9719c11c38c90ae2. 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=true 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=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (darwin-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@95d9a5deda9de15063e7595e9719c11c38c90ae2. 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=true 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=true. 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
new-version-patch
1.15 KB
sha256:4d366372158c6a756036dbfb4771c128921c89f85eeb82bf8bf490d88a9ad45b
unit-test-coverage
1.42 MB
sha256:5c9a6c155c8ac6586cd6ce09d2ceadda002c73b36a389a9d26ed921b2ca50c4e
vsix-package-darwin-arm64 Expired
41.1 MB
sha256:c06e7557497757875ae62d1d3461791bfdb1f10feb4b0cdfe374d82e49bbe8fb
vsix-package-darwin-x64 Expired
42.5 MB
sha256:2c2bd6e97e735d9f7baa07b1ef9689566218baafc5dbb26411fa3e0d751c7ed1
vsix-package-linux-arm64 Expired
44.7 MB
sha256:aef8d58d18a0289e4b4bd95630eef5f39383911ea20affa4e3c0834e64e662b1
vsix-package-linux-x64 Expired
47.6 MB
sha256:0402d3cf08e063d51ec7ecc873f41d0b93e9b396f62f8ea7a9a6ca1799bf5d4a
vsix-package-win32-arm64 Expired
41.7 MB
sha256:13bcf259f928480ca5c17a4fbecbd5bd459f77facfa34e8e24fe24e66f6eb4d9
vsix-package-win32-x64 Expired
44.4 MB
sha256:6ab04ce4a3e0cee2624677d5ea07c2dcca96480779e82a470fdd3e6fb9f6d68b