commands.CommandHandler.UnknownCommand calls fmt.Sprintf, which eventually calls template.context.String

bot.init calls gin.init, which eventually calls template.Template.Parse

commands.CommandHandler.HandleLocationMessage calls zerolog.Event.Err, which eventually calls template.Error.Error

weather.GeocodingClient.GeocodeLocation calls http.Client.Do, which eventually calls tls.Dialer.DialContext

database.ConnectRedis calls redis.NewClient, which eventually calls tls.DialWithDialer

services.ExportService.exportToTXT calls fmt.Fprintf, which calls tls.Conn.Write

weather.GeocodingClient.GeocodeLocation calls json.Decoder.Decode, which eventually calls tls.Conn.Read

bot.Start calls http.Server.ListenAndServe, which eventually calls tls.Conn.HandshakeContext

bot.Start calls http.Server.ListenAndServe, which eventually calls x509.Certificate.Verify

bot.Start calls http.Server.ListenAndServe, 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/setup-go@v4. 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/