bug: keep go versions in sync #17063
Assignees
Labels
s4
Internal bugs (e.g. test flakes), extreme edge cases, and bug risks
Comments
EdwardAngert
pushed a commit
that referenced
this issue
Apr 1, 2025
Fixes #17063 I'm ignoring flake.nix for now. ``` $ IGNORE_NIX=true ./scripts/check_go_versions.sh INFO : go.mod : 1.24.1 INFO : dogfood/coder/Dockerfile : 1.24.1 INFO : setup-go/action.yaml : 1.24.1 INFO : flake.nix : 1.22 INFO : Ignoring flake.nix, as IGNORE_NIX=true Go version check passed, all versions are 1.24.1 $ ./scripts/check_go_versions.sh INFO : go.mod : 1.24.1 INFO : dogfood/coder/Dockerfile : 1.24.1 INFO : setup-go/action.yaml : 1.24.1 INFO : flake.nix : 1.22 ERROR: Go version mismatch between go.mod and flake.nix ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
We define the Go version in multiple places, at least the following:
And, we keep updating some but not all of them at once. We need some way to keep them in sync.
Ideally, we'd have some single source of truth for the Go version in the repo. If that's impractical, some sort of CI check to ensure they are all in sync.
Relevant Log Output
Expected Behavior
No response
Steps to Reproduce
Look at the files and see they don't use the same version.
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: