Skip to content

feat(ci): test 52 upgrade #4

feat(ci): test 52 upgrade

feat(ci): test 52 upgrade #4

Triggered via pull request January 15, 2025 18:58
Status Failure
Total duration 53s
Artifacts

52.yml

on: pull_request
codeql-lint
42s
codeql-lint
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
codeql-lint
Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.20.1/x64/codeql/codeql database init --force-overwrite --db-cluster /home/runner/work/_temp/codeql_databases --source-root=/home/runner/work/connect/connect --extractor-include-aliases --language=go --begin-tracing --trace-process-name=Runner.Worker.exe --codescanning-config=/home/runner/work/_temp/user-config.yaml --calculate-language-specific-baseline --sublanguage-file-coverage". Exit code was 2 and error was: A fatal error occurred: Failed to clone external Git repository (eventual cause: TransportException "Remote branch 'v0.0.1' not found in upstream origin"). See the logs for more details.
codeql-lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
codeql-lint
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
codeql-lint
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.20.1.
codeql-lint
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.
codeql-lint
Unable to validate code scanning workflow: MissingPushHook
codeql-lint
2 diagnostic(s) could not be written to the database and will not appear on the Tool Status Page.