Skip to content

chore: float go so local matches continuous integration - #451

Merged
retr0h merged 1 commit into
mainfrom
chore/float-go-with-ci
Aug 16, 2026
Merged

chore: float go so local matches continuous integration#451
retr0h merged 1 commit into
mainfrom
chore/float-go-with-ci

Conversation

@retr0h

@retr0h retr0h commented Aug 16, 2026

Copy link
Copy Markdown
Collaborator

.mise.toml declared go = "1.25" while every workflow sets go-version: stable. That is a pin on one path and a float on the other, which the repo-standards requirement Every path provisions the same tool version forbids:

A version pinned in one path and floating in the other SHALL NOT be used.

This is not hypothetical

The two paths have already diverged:

Path Resolves to
.mise.toml (go = "1.25") 1.25.7
workflows (go-version: stable) 1.26.6

Verified from a CI log: Setup go version spec stablego version go1.26.6 linux/amd64.

So every contributor has been building and formatting with 1.25.7 while CI checks the result with 1.26.6. gofumpt output can change between toolchains, and that is exactly the failure the requirement describes — a check failing on a file nobody edited.

Why float rather than pin CI

The requirement gives the rule:

Where something maintains the version automatically, both paths SHALL pin it and that mechanism SHALL move both. Where nothing does, both paths SHALL track the latest release.

Nothing bumps .mise.toml — Dependabot has no ecosystem for it. So both paths track latest, which means go = "latest" locally rather than pinning CI backwards to 1.25.

Verification

just test passes on 1.26.6 — lint, unit tests, and the coverage gate.

🤖 Generated with Claude Code

.mise.toml declared go = "1.25" while every workflow sets go-version:
stable. That is a pin on one path and a float on the other, and the two
have already diverged: CI builds with 1.26.6, mise supplies 1.25.7.

gofumpt output can change between toolchains, so the divergence surfaces
as a check failing on a file nobody edited. Nothing bumps .mise.toml, so
per the requirement both paths track the latest release rather than one
side holding a pin the other never sees.

just test passes on 1.26.6.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@codecov

codecov Bot commented Aug 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #451   +/-   ##
=======================================
  Coverage   99.94%   99.94%           
=======================================
  Files         484      484           
  Lines       24935    24935           
=======================================
  Hits        24921    24921           
  Misses         14       14           

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 443440a...816bcc6. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@retr0h
retr0h merged commit fe98224 into main Aug 16, 2026
12 checks passed
@retr0h
retr0h deleted the chore/float-go-with-ci branch August 16, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant