How are the releases built?

[ILogOutOnTheToilet]

I tried building v2ray.exe for Windows, but ended up with a different file size and SHA512 for tag v2.58.0 using the manual instruction:
https://www.v2fly.org/en_US/developer/intro/compile.html#manual-build
Manual build v2ray.exe SHA512:

7F03DC9A4743E25205564F1020DE0438B5CF003375DC840E6C601378391A397D400EAC7C3D6C75473385552D1DA8CE4E1219DD555ED72E6DEB10FB977429A03F

v2.58.0 v2ray.exe release SHA512:

45D638AA9479075D2DF5F024A239C876E98489B0CEFC39A3AFAEEB96D47E23754171BBE9672906191123891E7D722B5D542ED075A97A2A9BC0D7E535B180D288

Release link: https://github.com/v2fly/v2ray-core/releases/tag/v5.28.0

I am on Windows, so I set the variables in PowerShell and then ran the go command:

$env:CGO_ENABLED="0"
$env:GOOS="windows" 
$env:GOARCH="amd64" 
go build -o $HOME/v2ray.exe -trimpath -ldflags "-s -w -buildid=" ./main

I also tried the .\release\user-package.sh windows script, which I had to run in WSL due to Linux dependencies, but every time I build with .\release\user-package.sh windows , the SHA512 is different. Does the project just have non-reproducible builds? Or am I missing some configurations?