Skip to content

Fix checkver and update to 3.26.11.412 (#128) #124

Fix checkver and update to 3.26.11.412 (#128)

Fix checkver and update to 3.26.11.412 (#128) #124

Triggered via push June 11, 2024 22:20
Status Success
Total duration 1m 10s
Artifacts

ci.yml

on: push
WindowsPowerShell
49s
WindowsPowerShell
PowerShell
55s
PowerShell
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 8 warnings
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 126ms (124ms|2ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.files end with a newline 155ms (154ms|1ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 171ms (169ms|1ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 151ms (150ms|2ms)
WindowsPowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 83ms (82ms|1ms)
WindowsPowerShell
[-] D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
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 139ms (138ms|2ms)
PowerShell
[-] Style constraints for non-binary project files.files end with a newline 134ms (132ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 151ms (150ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 76ms (75ms|1ms)
PowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 104ms (103ms|1ms)
PowerShell
[-] D:\a\scoopet\scoopet\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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/
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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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/