Unexpected Go 1.24.2 installation despite setting "go version 1.23 "

[IzDiego]

I'm encountering an issue where Go 1.24.2 is being installed during a GitHub Actions job, even though I've explicitly specified Go 1.23.

Workflow step:

- name: Build Wails app
  uses: dAppServer/wails-build-action@main
  with:
    go-version: '1.23'
    build-name: ${{ matrix.name }}
    build-platform: ${{ matrix.platform }}
    # Obfuscation requires Go 1.23
    build-obfuscate: true 

Runner output:

1. Run dAppServer/wails-build-action@main
2. with:
3. go-version: 1.23.9
4. build-name: MongoPOS
5. build-platform: darwin/universal
6. build-obfuscate: true
7. build: true
8. sign: false
9. package: true
10. nsis: false
11. build-cache: true
12. build-tags: false
13. wails-version: latest
14. wails-build-webview2: download
15. node-version: 18.x
16. app-working-directory: .
17. deno-working-directory: .
18. deno-version: v1.20.x
19. wails-dev-build: false
20. Run build_options=""
21. Run actions/setup-go@v5
22.   with:
23.     check-latest: true
24.     cache: true
25.     cache-dependency-path: go.sum
26.     go-version: 1.23.9
27.     token: ***
28. Setup go version spec 1.23.9
29. Attempting to resolve the latest version from the manifest...
30. matching 1.23.9...
31. Resolved as '1.23.9'
32. Attempting to download 1.23.9...
33. matching 1.23.9...
34. Acquiring 1.23.9 from https://github.com/actions/go-versions/releases/download/1.23.9-14875265214/go-1.23.9-darwin-arm64.tar.gz
35. Extracting Go...
36. /usr/bin/tar xz -C /Users/runner/work/_temp/562ddd85....
37. Successfully extracted go to /Users/runner/work/_temp/562ddd85-cabb-412e-b568-4a0ecf19d1c9
38. Adding to the cache ...
39. Successfully cached go to /Users/runner/hostedtoolcache/go/1.23.9/arm64
40. Added go to the path
41. Successfully set up Go version 1.23.9
42. go: downloading go1.24.2 (darwin/arm64)
43. /Users/runner/hostedtoolcache/go/1.23.9/arm64/bin/go env GOMODCACHE
44. /Users/runner/hostedtoolcache/go/1.23.9/arm64/bin/go env GOCACHE
45. /Users/runner/Library/Caches/go-build
46. /Users/runner/go/pkg/mod
47. Cache is not found
48. go version go1.24.2 darwin/arm64
49. 
50. go env
51. Run go install mvdan.cc/garble@latest
52. go: downloading mvdan.cc/garble v0.14.2
53. go: downloading github.com/rogpeppe/go-internal v1.14.1
54. go: downloading golang.org/x/mod v0.24.0
55. go: downloading golang.org/x/tools v0.32.0
56. go: downloading github.com/bluekeyes/go-gitdiff v0.8.1
57. Run go version
58. go version go1.24.2 darwin/arm64

At line 42, Go 1.24.2 is downloaded, and at line 48, the version output confirms it is being used. The job continues using Go 1.24.2, which leads to a failure later during the build:

  • Installing frontend dependencies: Done.
  • Compiling frontend: Done.
  -seed chosen at random: x9CZS10QrENhZQmJlO8uwQ
    garble was built with "go1.23.9" and can't be used with the newer "go1.24.2"; rebuild it with a command like:
    go install mvdan.cc/garble@latest
  • Compiling application:   ERROR   exit status 1

Troubleshooting attempts:

• Tried different wails-version values.
• Changed go-version (explicitly to 1.23.9 and 1.23).
• Removed matrix usage to simplify.
• Used actions/setup-go@v5 directly — confirmed that it correctly installs only Go 1.23.9 and doesn't trigger 1.24.2 download.
• Disabled obfuscation — build completes successfully, since the issue is specific to the garble obfuscation tool requiring an exact Go version.

Expected behavior:

The specified Go version (1.23.x) should be used throughout the job, especially when build-obfuscate: true is set, as the obfuscator (garble) is sensitive to the Go version it was built with.

Request:

Could you help identify why Go 1.24.2 is being downloaded and used despite explicitly setting 1.23?

[tassa-yoniso-manasi-karoto]

I had this too. It's the toolchain. The toolchain version is authoritative.

correct go.mod and use a go version manager like https://github.com/voidint/g to stay at 1.23.9