Skip to content

chore(DevDependency): bump vitest from 4.1.4 to 4.1.5 (#500) #2553

chore(DevDependency): bump vitest from 4.1.4 to 4.1.5 (#500)

chore(DevDependency): bump vitest from 4.1.4 to 4.1.5 (#500) #2553

Triggered via push May 1, 2026 09:01
Status Success
Total duration 6m 34s
Artifacts 2

main.yml

on: push
Check requirements
23s
Check requirements
Auto-merge dependabot PR
0s
Auto-merge dependabot PR
Matrix: e2e-test
Matrix: integration-test
Run CodeQL analysis
2m 30s
Run CodeQL analysis
Run unit tests
34s
Run unit tests
Check action with dry run
0s
Check action with dry run
Create release
Create release
Publish metadata to GitHub Pages
33s
Publish metadata to GitHub Pages
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 12 warnings
Run unit tests
Failed to update (Legacy) WinSDK Module Map: Error: Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Failed to update (Legacy) WinSDK Module Map: Error: Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Proceeding with fallback installation approach
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Proceeding with fallback installation approach
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run CodeQL analysis
User-specified `matrix` input is not an object.
Publish metadata to GitHub Pages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
debug-artifacts Expired
29.6 MB
sha256:42eedb786d02ce83b374450f6dc0f30527da8a5df707975de186298277ed595d
github-pages Expired
942 Bytes
sha256:1dc9ed14cf7979ab86dc47c208b00f3c0c56c2ad20f3227764533aa1f2fd7c62