Skip to content

fix(release): restore go.mod tidy state after glob import #520

Description

@rianjs

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions