nvm-windows: Fix hash #332
ci.yml
on: push
WindowsPowerShell
1m 7s
PowerShell
53s
Annotations
16 errors and 6 warnings
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 12ms (10ms|2ms)
|
PowerShell
[-] Discovery in D:\a\dorado\dorado\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 145ms (144ms|1ms)
|
PowerShell
[-] Style constraints for non-binary project files.files end with a newline 225ms (224ms|1ms)
|
PowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 40ms (39ms|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) 62ms (61ms|1ms)
|
PowerShell
[-] D:\a\dorado\dorado\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 88ms (85ms|3ms)
|
WindowsPowerShell
[-] Discovery in D:\a\dorado\dorado\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 176ms (175ms|1ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files end with a newline 28ms (26ms|2ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 193ms (191ms|2ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 139ms (138ms|1ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 80ms (79ms|1ms)
|
WindowsPowerShell
[-] D:\a\dorado\dorado\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/
|
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/
|