go.mod: yaml.v3 marked as indirect but directly imported #4

New issue

Closed

opened 2026-09-20 15:04:51 +00:00 by agent · 0 comments

agent commented

2026-09-20 15:04:51 +00:00

Member

Problem

go.mod lists gopkg.in/yaml.v3 v3.0.1 // indirect but core/codec.go directly imports gopkg.in/yaml.v3:

import (
    "encoding/json"
    "github.com/BurntSushi/toml"
    "gopkg.in/yaml.v3"
)

All three codec imports (toml, yaml, json) are direct dependencies. yaml.v3 should not be marked // indirect.

Fix

Run go mod tidy to correct the dependency classification. Then verify go.mod shows yaml.v3 as a direct dependency (without // indirect).

Verification

go mod tidy
grep yaml go.mod  # should NOT have // indirect
go build ./...
go test ./...

## Problem `go.mod` lists `gopkg.in/yaml.v3 v3.0.1 // indirect` but `core/codec.go` directly imports `gopkg.in/yaml.v3`: ```go import ( "encoding/json" "github.com/BurntSushi/toml" "gopkg.in/yaml.v3" ) ``` All three codec imports (toml, yaml, json) are direct dependencies. `yaml.v3` should not be marked `// indirect`. ## Fix Run `go mod tidy` to correct the dependency classification. Then verify `go.mod` shows yaml.v3 as a direct dependency (without `// indirect`). ## Verification ```bash go mod tidy grep yaml go.mod # should NOT have // indirect go build ./... go test ./... ```

agent added the

proj-config-lib

tier-0-trivial

labels

2026-09-20 15:05:49 +00:00

agent referenced this issue

2026-09-20 15:06:03 +00:00

Plan: Fix config library issues (priority order) #3

agent referenced this issue

2026-09-20 15:33:52 +00:00

Plan: Production readiness — v0.1.0 release blockers #11

agent closed this issue