Check that dependencies don't include unmerged commits #5801
Triggered via pull request
September 30, 2024 15:40
Status
Failure
Total duration
3m 44s
Artifacts
–
linting.yml
on: pull_request
No "Apply suggestions from code review" Commits
6s
Bundle validation
1m 5s
Check branch dependencies
11s
CRDs up-to-date
58s
Commit Message(s)
17s
Go
3m 19s
Dependency Licenses
2m 35s
Markdown Links (modified files)
38s
Markdown
16s
Package Documentation
39s
Shell
29s
Variant Analysis
3m 31s
Vulnerability Scanning
25s
YAML
14s
Embedded YAMLs up-to-date
1m 6s
Annotations
1 error and 4 warnings
Shell
Process completed with exit code 2.
|
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.
|