Skip to content

bug: keep go versions in sync #17063

Closed
Closed
@spikecurtis

Description

@spikecurtis

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

We define the Go version in multiple places, at least the following:

  • dogfood/coder/Dockerfile
  • flake.nix
  • go.mod
  • .github/actions/setup-go/action.yaml

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

  • Host OS:
  • Coder version:

Additional Context

No response

Metadata

Metadata

Assignees

Labels

s4Internal bugs (e.g. test flakes), extreme edge cases, and bug risks

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions