Skip to content

edge-webview2-runtime: add 119.0.2151.58 #177

edge-webview2-runtime: add 119.0.2151.58

edge-webview2-runtime: add 119.0.2151.58 #177

Triggered via push October 4, 2024 10:42
Status Success
Total duration 45s
Artifacts

ci.yml

on: push
WindowsPowerShell
36s
WindowsPowerShell
PowerShell
29s
PowerShell
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 8 warnings
PowerShell
[-] Discovery in D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
PowerShell
[-] Style constraints for non-binary project files.files do not contain leading UTF-8 BOM 212ms (211ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.files end with a newline 36ms (34ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 138ms (137ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 75ms (74ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 74ms (73ms|1ms)
PowerShell
[-] D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
WindowsPowerShell
[-] Discovery in D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
WindowsPowerShell
[-] Style constraints for non-binary project files.files do not contain leading UTF-8 BOM 69ms (67ms|2ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.files end with a newline 22ms (21ms|1ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 92ms (91ms|2ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 150ms (149ms|2ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 123ms (122ms|1ms)
WindowsPowerShell
[-] D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
PowerShell
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
PowerShell
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
PowerShell
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
PowerShell
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
WindowsPowerShell
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
WindowsPowerShell
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
WindowsPowerShell
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
WindowsPowerShell
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/