clash-verge-rev: Update to version 2.0.2 #475
ci.yml
on: push
WindowsPowerShell
42s
PowerShell
42s
Annotations
16 errors and 6 warnings
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 11ms (9ms|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 314ms (313ms|1ms)
|
PowerShell
[-] Style constraints for non-binary project files.files end with a newline 31ms (30ms|2ms)
|
PowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 124ms (123ms|1ms)
|
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 71ms (70ms|1ms)
|
PowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 83ms (83ms|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 128ms (125ms|2ms)
|
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 107ms (105ms|2ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files end with a newline 63ms (61ms|2ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 176ms (174ms|2ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 145ms (144ms|1ms)
|
WindowsPowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 78ms (77ms|1ms)
|
WindowsPowerShell
[-] D:\a\dorado\dorado\scoop_core\test\Import-Bucket-Tests.ps1 failed with:
|
PowerShell
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
|
WindowsPowerShell
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
|
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/
|
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/
|