Repository navigation
build: require errors v0.8.0 - #52
Merged
Merged
Conversation
errors v0.8.0 drops the go-errors dependency and the Wrapper field, which log stopped reading in v1.7.3, so go-errors leaves log's module graph. Point the README install commands at v1.7.4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
ERR-07 last step (owner-approved 2026-11-21): raise
github.com/jgolang/errorsto v0.8.0 and point the README install commands at the release this PR becomes (v1.7.4). Leaves outotel/go.mod(unchanged; it still pins log v1.7.1, solog/otelusers keep go-errors in their module graph until otel raises itslogfloor, a possible follow-up). Not a stack; nothing planned on top.Reason
errors v0.8.0 removed
Wrapperand itsgithub.com/go-errors/errorsdependency. log v1.7.3 already readsDetail, so raising the requirement removes go-errors from log's build.Changes
go.mod/go.sum: errors v0.7.0 → v0.8.0; indirectgithub.com/go-errors/errorsremoved bygo mod tidy.README.md: install/upgrade commands namelog@v1.7.4(v1.7.2 pulled go-errors).Verification
otel/:gofmt -l .empty,go vet ./...,go test -race ./...,govulncheck ./...clean. Existing log/golden tests unchanged.oteltests also pass in a scratch copy withgithub.com/jgolang/logreplaced by this tree (errors v0.8.0 selected); not committed.go list -m all(root): no go-errors.LoggerInfo/coded_error_attr37,ValidateArgs/coded_error24); B/op +184 B per coded-error record (2.343Ki → 2.522Ki, 1.336Ki → 1.516Ki) from theruntime.CallersFramesiterator errors v0.8.0 uses to resolve frames. Disabled-level paths unchanged at 0 B.Release notes (v1.7.4)
github.com/jgolang/errorsv0.8.0;github.com/go-errors/errorsis no longer a dependency oflog.originattribute of coded errors now name inlined callers correctly (errors v0.8.0). Each coded-error record allocates about 184 bytes more.🤖 Generated with Claude Code