Skip to content

syncing release 1.4 with internal repo #451

syncing release 1.4 with internal repo

syncing release 1.4 with internal repo #451

Triggered via pull request August 28, 2024 22:00
Status Success
Total duration 8m 43s
Artifacts

presubmit.yaml

on: pull_request
Presubmit
8m 33s
Presubmit
Detect deprecated apiGroups
6s
Detect deprecated apiGroups
vuln_check
19s
vuln_check
static-security-analysis
1m 9s
static-security-analysis
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Detect deprecated apiGroups
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
vuln_check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
static-security-analysis
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Presubmit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/