Bump mark3labs/mcp-go from 0.25.0 to 0.32.0 with new features and bug fixes #25
Conversation
…_fixes_1752457944
WalkthroughThe Changes
Possibly related PRs
Suggested labels
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
📒 Files selected for processing (1)
go.mod(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: ci
| require ( | ||
| github.com/mark3labs/mcp-go v0.25.0 | ||
| github.com/mark3labs/mcp-go v0.32.0 | ||
| github.com/spf13/viper v1.20.1 | ||
| ) |
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
Run go mod tidy and commit the resulting go.sum
The dependency bump is fine, but the PR does not include an updated go.sum.
Without running go mod tidy, the checksum list is stale and CI/CD builds may fail or, worse, pull in unintended transitive versions.
Action items:
go mod tidyto reconcile the module graph.- Commit the updated
go.sum(and any indirect version tweaks). - Compile & run the full test-suite to catch API breakages introduced between v0.25.0 → v0.32.0.
Suggested local commands:
🏁 Script executed:
#!/usr/bin/env bash
set -euo pipefail
go mod tidy
git diff --compact-summary go.sum
go test ./...Length of output: 706
Resolve the go.sum Checksum Mismatch
go mod tidy is failing with a checksum mismatch for github.com/mark3labs/mcp-go v0.32.0, indicating the recorded sum in go.sum doesn’t match the module’s current download. To fix this:
• Invalidate and refresh your module cache:
go clean -modcache
go mod tidy• Inspect the new checksum for github.com/mark3labs/mcp-go v0.32.0 in go.sum.
• If the mismatch persists, verify that the tagged version exists upstream (e.g., check the module’s Git tags) or consider pinning to a known-good version via:
go mod edit -require=github.com/mark3labs/[email protected]
go mod tidy• Commit the updated go.sum and rerun your full test suite:
git diff --compact-summary go.sum
go test ./...Files to review:
- go.mod
- go.sum
🤖 Prompt for AI Agents
In go.mod around lines 5 to 8, there is a checksum mismatch error for
github.com/mark3labs/mcp-go v0.32.0 causing go mod tidy to fail. Fix this by
cleaning the module cache with 'go clean -modcache', then run 'go mod tidy' to
refresh go.sum. If the mismatch persists, verify the version exists upstream or
downgrade to a stable version like v0.31.0 using 'go mod edit
-require=github.com/mark3labs/[email protected]' followed by 'go mod tidy'.
Finally, commit the updated go.sum and run all tests to ensure stability.
Bumps github.com/mark3labs/mcp-go from 0.25.0 to 0.32.0.
Release notes
Sourced from github.com/mark3labs/mcp-go's releases.
... (truncated)
Commits
5c49f63more docs fixesb5db567improve docs some more3943813Optimize docs (#386)8c7a09dUse fuzzy searchdc234adsupport search doc (#378)c3e9723fix: ignore session IDs in stateless mode instead of rejecting them (#375)75abd9afix: SSE parser now correctly handles events without event field (#376)cf6a2e9fix(srv/stream): properly remove sessionTool to prevent memory leak (#365)564b669cleanup6ac1843fix linksDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Completed by Agent
Fixes #22
Summary by CodeRabbit