fix: remove go.sum conflict markers#89
Conversation
Judicial ReviewReviewed the go.sum cleanup that removes conflict markers and retains the v0.49.0 checksums; change is narrowly scoped and fixes a malformed dependency file without introducing new behavior. No significant issues found. This code is cleared to ship. Legal-Grade review by Thurgood | Re-review with |
Oppenheimer Cleanup ReviewReviewed the go.sum fix; no simplification opportunities or risky complexity found. Conflict markers are already removed and no additional dead code or redundancy was identified. No cleanup opportunities found. This code is already lean. Cleanup review by Oppenheimer | Re-run with |
DB Cooper Database ReviewNo database-related changes detected; the diff only removes conflict markers from go.sum with no schema, query, or migration impact. No database risks found. Migrations and DB-impacting changes look safe. DB review by DB Cooper | Re-run with |
1 participant
Summary
Fix the malformed
go.sumthat caused thev0.38.0GoReleaser publish workflow to fail before uploading release assets.Context
The
v0.38.0release tag includes unresolved merge conflict markers at the top ofgo.sum, so GoReleaser failed during its before hook:That left the GitHub release with no assets, which then caused
casedotdev-monoDaytona snapshot promotion to fail when it tried to resolve the latest CLI.deb.Changes
go.sum.github.com/CaseMark/casedev-go v0.49.0checksum entries that matchgo.mod.Validation
GONOSUMDB='github.com/CaseMark/*' go run ./cmd/casedev/main.go @completion bash >/tmp/casedev-completion.bashGONOSUMDB='github.com/CaseMark/*' ./scripts/lintGONOSUMDB='github.com/CaseMark/*' ./scripts/testrg -n '<<<<<<<|=======|>>>>>>>' .Release Follow-Up
After this merges, publish a clean follow-up release, likely
v0.38.1, socasedev-clihas Linux.debassets again. Then rerun thecasedotdev-monoDaytona snapshot promotion.