Skip to content

Fix upload-sarif Action failing if there are no Code Scanning SARIF files #1393

Fix upload-sarif Action failing if there are no Code Scanning SARIF files

Fix upload-sarif Action failing if there are no Code Scanning SARIF files #1393

Triggered via pull request September 18, 2025 14:34
Status Success
Total duration 4m 45s
Artifacts 4
Matrix: Upload debug artifacts after failure in analyze
Download and check debug artifacts after failure in analyze
12s
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.0.
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.0.
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 (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.0.
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
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.0.
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

Artifacts

Produced during runtime
Name Size Digest
my-debug-artifacts-default Expired
206 MB
sha256:806f16c96a5f72b2df20365c21218edea1539ebdf6d77111874d4ebf3bf32228
my-debug-artifacts-linked Expired
206 MB
sha256:9766fe92cf4eb724a2be9b5ff6c73a19f1f17afc0ce90bc4d6e55087775a47b5
my-debug-artifacts-nightly-latest Expired
206 MB
sha256:e6e8070370bb59980b9374b48e0b5282e9ea744a0b7743a6ec5f97b58f25e296
my-debug-artifacts-stable-v2203 Expired
19.9 MB
sha256:7ab76db5c61e82ccba2da86217187cdf522f0f428cb382bf7475e304b78eb7a4