flutter-cn: fix manifest (#819) #365
chawyehsuci.yml
on: push
WindowsPowerShell
36s
PowerShell
33s
Annotations
16 errors and 8 warnings
|
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 14ms (12ms|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 67ms (66ms|1ms)
|
|
PowerShell
[-] Style constraints for non-binary project files.files end with a newline 103ms (101ms|2ms)
|
|
PowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 186ms (184ms|2ms)
|
|
PowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 109ms (108ms|1ms)
|
|
PowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 110ms (109ms|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 15ms (12ms|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 126ms (125ms|1ms)
|
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files end with a newline 182ms (180ms|2ms)
|
|
WindowsPowerShell
[-] Style constraints for non-binary project files.file newlines are CRLF 80ms (79ms|1ms)
|
|
WindowsPowerShell
[-] Style constraints for non-binary project files.files have no lines containing trailing whitespace 149ms (147ms|2ms)
|
|
WindowsPowerShell
[-] Style constraints for non-binary project files.any leading whitespace consists only of spaces (excepting makefiles) 179ms (178ms|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
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/
|
|
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/
|