I'm sorry, i can't recreate the problem.

I'm running this program:

package main

import (
	"fmt"
	"log"
	"time"
)

func main() {
	loc, err := time.LoadLocation("America/Tijuana")
	if err != nil {
		log.Fatal(err)
	}
	d := time.Date(2022, 11, 22, 10, 0, 0, 0, loc)
	fmt.Println(d)
}

It always prints 2022-11-22 10:00:00 -0800 PST regardless of how I run update.bash and set ZONEINFO.

Can you show complete and precise instructions for how to see the problem? Thanks.

You should test like this:
d := time.Now().In(loc).Format("2006-01-02 15:04:05")

When you trans a timestamp to string-style-time, it will has 1 hour diff with local real time

Or you can test the code:

loc, _:= time.LoadLocation("America/Tijuana")
name, offset := time.Now().In(loc).Zone()
offset should be GMT-8 for "America/Tijuana", But go GMT-7

I don't see the same thing you're seeing. The program:

package main

import (
	"fmt"
	"time"
)

func main() {
	loc, _ := time.LoadLocation("America/Tijuana")
	name, offset := time.Now().In(loc).Zone()
	fmt.Printf("%s %v\n", name, offset/3600)
}

Prints

PST -8

On both go1.18.8, go1.19.3, and tip (on darwin/amd64).

Please give us complete and precise instructions for how to see the problem. Tell us every single step. Be complete and precise. Thanks.

step 1. run update.bash update zoneinfo.zip to 2022f

step 2. run test code
package main

import (
"fmt"
"time"
"os"
)

func main() {
os.Setenv("ZONEINFO", "/home/xxxx/zoneinfo.zip")
loc, _ := time.LoadLocation("America/Tijuana")
name, offset := time.Now().In(loc).Zone()
fmt.Printf("%s %v\n", name, offset/3600)
}

step 3. check result
offset should be GMT-8 for "America/Tijuana",
But go GMT-8 on Darwin/amd64 go 1.17
Got GMT-7 on Linux go 1.13
Got GMT-7 on Goland IDE go 1.13

Hmmm, are you really using Go 1.13? The fix for the problem you are describing was first released as part of the Go 1.14 release series (https://go.dev/cl/215539). Go 1.13 is no longer supported. The most recent release is Go 1.19. Can you recreate the problem using Go 1.19?

I see, go 1.19 do not has this bug. If using go 1.13, -R option can solve this problem
We are coders of Chinese company , and we still using go 1.13 , haha!!

Thanks all you guys, this issue can closed.