Bump github/codeql-action from 2.20.3 to 2.20.4 #81
dependabot[bot]
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
32 warnings
|
build (Debug, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Debug, x64)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Debug, x64)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Debug, x64)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Debug_Unicode, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Debug_Unicode, x64)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Debug_Unicode, x64)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Debug_Unicode, x64)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Release, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Release, x64)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Release, x64)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Release, x64)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Debug, Win32)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Debug, Win32)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Debug, Win32)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Debug, Win32)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Debug_Unicode, Win32)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Debug_Unicode, Win32)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Debug_Unicode, Win32)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Debug_Unicode, Win32)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Release, Win32)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Release, Win32)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Release, Win32)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Release, Win32)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Release_Unicode, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Release_Unicode, x64)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Release_Unicode, x64)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Release_Unicode, x64)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
|
build (Release_Unicode, Win32)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/vstest-action@6ef4755ea07a3144e3da36f10d76187086eee5e6. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
build (Release_Unicode, Win32)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
build (Release_Unicode, Win32)
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
build (Release_Unicode, Win32)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.0.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
vs-test-result-logs
Expired
|
2.05 MB |
|