Skip to content
Linting

Automated backport of #1653: E2E: use ServiceDiscovery CR to determine if clusterset IP is #2631

Sign in to view logs

Automated backport of #1653: E2E: use ServiceDiscovery CR to determine if clusterset IP is

Automated backport of #1653: E2E: use ServiceDiscovery CR to determine if clusterset IP is #2631

Triggered via pull request October 1, 2024 18:40
@tpantelistpantelis
opened #1654
tpantelis:automated-backport-of-#1653-upstream-release-0.19
Status Success
Total duration 3m 34s
Artifacts –

linting.yml

on: pull_request
No "Apply suggestions from code review" Commits
5s
No "Apply suggestions from code review" Commits
Commit Message(s)
10s
Commit Message(s)
Go
2m 50s
Go
Dependency Licenses
3m 22s
Dependency Licenses
Markdown Links (modified files)
21s
Markdown Links (modified files)
Markdown
9s
Markdown
Package Documentation
27s
Package Documentation
Vulnerability Scanning
24s
Vulnerability Scanning
YAML
7s
YAML
Fit to window
Zoom out
Zoom in

Annotations

1 warning
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/