Problem
The post-merge release workflow failed in run 29639199261, job release / goreleaser, step Build (snapshot, no publish).
GoReleaser reached its existing make tidy before-hook, where go mod tidy changed go.mod and the repository's tidy guard failed:
- github.com/gobwas/glob v0.2.3 // indirect
+ github.com/gobwas/glob v0.2.3
Root cause
PR #517 added a direct import of github.com/gobwas/glob in internal/agents/agents.go, but go.mod still classifies the module as indirect. This is deterministic repository drift, not a transient runner or network failure.
Narrow fix
Run go mod tidy and commit only the resulting direct/indirect classification move in go.mod. No source, dependency-version, or go.sum change is expected.
Empirical success criteria
go mod tidy produces no subsequent diff in go.mod or go.sum.
make tidy exits successfully.
- Go tests and build remain green.
- The PR CI workflow succeeds.
- After merge, the new release workflow completes the GoReleaser snapshot build instead of failing its
make tidy before-hook.
Problem
The post-merge release workflow failed in run 29639199261, job
release / goreleaser, stepBuild (snapshot, no publish).GoReleaser reached its existing
make tidybefore-hook, wherego mod tidychangedgo.modand the repository's tidy guard failed:Root cause
PR #517 added a direct import of
github.com/gobwas/globininternal/agents/agents.go, butgo.modstill classifies the module as indirect. This is deterministic repository drift, not a transient runner or network failure.Narrow fix
Run
go mod tidyand commit only the resulting direct/indirect classification move ingo.mod. No source, dependency-version, orgo.sumchange is expected.Empirical success criteria
go mod tidyproduces no subsequent diff ingo.modorgo.sum.make tidyexits successfully.make tidybefore-hook.