build(deps): pin cloud-commitments-go to main (6168f8b) - #25
Conversation
The previous pseudo-version pins (pkg@43ab778da, providers/{aws,azure,gcp}@692cacc627d1)
were on the unmerged cloud-commitments-go PR #1 split branch, which no longer exists
on main after the squash-merge to 6168f8b5360d5189c140cd8f4de614531cffa998. Re-pin all
four modules to that commit.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: LeanerCloud/cloud-commitments-mcp/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour. 📝 WalkthroughWalkthroughFour ChangesGo module versions
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to All four updated dependencies resolve to the intended revision and checksums; no material merge risk is evident from this change. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Independent review + local verification: MERGE at 50b1f72. Re-pins cloud-commitments-go to main (6168f8b5); go.sum changes limited to the four modules; build/vet/race tests pass; MCP stdio probe returns the same 11 tools with nothing on stdout but protocol frames; 13/13 checks. |
Summary
Re-pins
github.com/LeanerCloud/cloud-commitments-go/{pkg,providers/aws,providers/azure,providers/gcp}from the abandoned split-PR pseudo-versions to the commit that actually landed on go main.Why
cloud-commitments-goPR #1 was squash-merged tomainas6168f8b5360d5189c140cd8f4de614531cffa998. This repo's previous pins were pseudo-versions taken from the unmerged split branch before the squash:pkgv0.0.0-20260925082912-43ab778da7acv0.0.0-20260928074610-6168f8b5360dproviders/awsv0.0.0-20260926232454-692cacc627d1v0.0.0-20260928074610-6168f8b5360dproviders/azurev0.0.0-20260926232454-692cacc627d1v0.0.0-20260928074610-6168f8b5360dproviders/gcpv0.0.0-20260926232454-692cacc627d1v0.0.0-20260928074610-6168f8b5360dThose commits (
43ab778da7ac,692cacc627d1) are no longer reachable from go main after the squash-merge, so this repo'sgo.modpointed at history that no longer exists there.Change
All four modules resolved to
v0.0.0-20260928074610-6168f8b5360d(MVS resolved cleanly).go.workstill only containsuse ., unchanged.The renamed exported identifiers in cloud-commitments-go (
AWSProvider->Provider,XxxAPI->API, etc.) required no call-site changes here;go build/go vetpass with no errors.Verification
go build -o /dev/null ./...: passgo vet ./...: pass (no findings)go test -race -short ./...: pass, all 3 packagesok(root,cmd/cudly-mcp,tools), no FAILgo mod tidy -diff: empty (clean)golangci-lint v2.10.1(CI-pinned version,golangci-lint run --timeout=10m, exact CI invocation):0 issuesHousekeeping re-pin, not tied to a specific issue.
Summary by CodeRabbit