cmd.startHTTPServer calls http.Server.ListenAndServe, which eventually calls template.Template.Execute

proxy.MultiErr.Error calls template.Error.Error

proxy.CheckConnections calls cloudsqlconn.Dialer.Dial, which eventually calls x509.Certificate.Verify

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls tls.Dialer.DialContext

gendocs.main calls fmt.Fprintf, which calls tls.Conn.Write

proxy.Client.proxyConn calls cloudsqlconn.instrumentedConn.Read, which calls tls.Conn.Read

proxy.CheckConnections calls cloudsqlconn.Dialer.Dial, which calls tls.Conn.HandshakeContext

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls tls.Conn.Handshake

proxy.CheckConnections calls cloudsqlconn.Dialer.Dial, which eventually calls x509.Certificate.Verify

proxy.CheckConnections calls cloudsqlconn.Dialer.Dial, which eventually calls x509.Certificate.Verify

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to restore: Cache service responded with 400