Skip to content

[release-3.5] Setup a way to consistently manage go versions across scripts and go.mods #12744

[release-3.5] Setup a way to consistently manage go versions across scripts and go.mods

[release-3.5] Setup a way to consistently manage go versions across scripts and go.mods #12744

Triggered via pull request May 15, 2024 10:39
Status Success
Total duration 24m 8s
Artifacts

grpcproxy.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
test (linux-amd64-grpcproxy)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-go@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test (linux-amd64-grpcproxy)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/