build(deps): update module golang.org/x/net to v0.53.0 [security] (#1… #720
mergify[bot]Annotations
10 errors and 1 warning
|
vulnerability-scan
Process completed with exit code 3.
|
|
vulnerability-scan
canal.eventHandler.clearImageCache calls s3.Client.DeleteObjects, which eventually calls http.Transport.RoundTrip
|
|
vulnerability-scan
canal.eventHandler.clearImageCache calls s3.Client.DeleteObjects, which eventually calls http.Transport.CloseIdleConnections
|
|
vulnerability-scan
subject.client.OnDelete calls meilisearch.index.DeleteDocumentWithContext, which eventually calls http.Client.Do
|
|
vulnerability-scan
web.Start calls echo.Echo.Start, which eventually calls net.ListenConfig.Listen
|
|
vulnerability-scan
canal.Main calls http.Server.ListenAndServe, which calls net.Listen
|
|
vulnerability-scan
driver.NewMysqlDriver calls sql.Open, which eventually calls net.Dialer.DialContext
|
|
vulnerability-scan
web.Start calls echo.Echo.Start, which eventually calls httputil.ReverseProxy.ServeHTTP
|
|
vulnerability-scan
web.Start calls echo.Echo.Start, which eventually calls template.Template.Execute
|
|
vulnerability-scan
web.Start calls echo.Echo.Start, which eventually calls template.Template.Execute
|
|
vulnerability-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jayqi/failed-build-issue-action@v1.2.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/
|