Automated backport of #3222: Allow the gateway to wait for node readiness #5124
linting.yml
on: pull_request
No "Apply suggestions from code review" Commits
5s
Submariner K8s API Code Generation
1m 23s
Protobuf Code Generation
33s
Commit Message(s)
15s
Go
3m 52s
Dependency Licenses
2m 23s
Markdown Links (modified files)
19s
Markdown
12s
Package Documentation
48s
Shell
13s
Variant Analysis
4m 16s
Vulnerability Scanning
25s
YAML
15s
Annotations
4 warnings
No "Apply suggestions from code review" Commits
The following actions use a deprecated Node.js version and will be forced to run on node20: tim-actions/get-pr-commits@198af03565609bb4ed924d1260247b4881f09e7d, tim-actions/commit-message-checker-with-regex@094fc16ff83d04e2ec73edb5eaf6aa267db33791. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Variant Analysis
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
|
Variant Analysis
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.18.3.
|
Variant Analysis
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.
|