Skip to content

Make analysis kinds available for starting status report #1726

Make analysis kinds available for starting status report

Make analysis kinds available for starting status report #1726

Triggered via pull request October 17, 2025 10:51
Status Success
Total duration 4m 1s
Artifacts 4
Matrix: Upload debug artifacts after failure in analyze
Download and check debug artifacts after failure in analyze
11s
Download and check debug artifacts after failure in analyze
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
Upload debug artifacts after failure in analyze (stable-v2.20.3)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (stable-v2.20.3)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (nightly-latest)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (nightly-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
Upload debug artifacts after failure in analyze (nightly-latest)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (nightly-latest)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (linked)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (linked)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
Upload debug artifacts after failure in analyze (linked)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (linked)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum
Upload debug artifacts after failure in analyze (default)
Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you.
Upload debug artifacts after failure in analyze (default)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.23.2.
Upload debug artifacts after failure in analyze (default)
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 - https://docs.github.com/rest
Upload debug artifacts after failure in analyze (default)
Restore cache failed: Dependencies file is not found in /home/runner/work/codeql-action/codeql-action. Supported file pattern: go.sum

Artifacts

Produced during runtime
Name Size Digest
my-debug-artifacts-default Expired
207 MB
sha256:04bddcf4532ab8d632ef8ea11885f2d2c42fa7b51af114bb4693839400dfa7f4
my-debug-artifacts-linked Expired
207 MB
sha256:309c8c63824418ec7e1facce3473653a7dddd6f70ebb04407e8d8d33712638a1
my-debug-artifacts-nightly-latest Expired
207 MB
sha256:ab8d025da06367f35062666c2ad16cd243c250e4696f43fba0e913e84d519fe5
my-debug-artifacts-stable-v2203 Expired
19.9 MB
sha256:64aa0717f6b7adc3c1c285b21a44567a1b482e0ded31a8bab71c1b3d9b914ac6