-
Couldn't load subscription status.
- Fork 0
chore(deps): bump github.com/mark3labs/mcp-go from 0.25.0 to 0.33.0 #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThe dependency 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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
go.mod(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Build & Verify Pipeline
go.mod
[error] 1-1: go.mod or go.sum is not tidy, run 'go mod tidy' to fix module dependencies.
⏰ 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
🔇 Additional comments (1)
go.mod (1)
3-3: Verify thegodirective references a released toolchain
go 1.24.2points to a future Go version; most builders currently top out at 1.22.x.
Ensure your CI/build images actually provide Go 1.24, or downgrade the directive (e.g.go 1.22) to avoid “unsupported go version” errors.
| require ( | ||
| github.com/mark3labs/mcp-go v0.25.0 | ||
| github.com/mark3labs/mcp-go v0.33.0 | ||
| github.com/spf13/viper v1.20.1 | ||
| ) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run go mod tidy – CI is failing on an untidy module
The dependency bump pulls new transitive requirements, but neither go.mod nor go.sum were re-tidied.
The pipeline already reports:
go.mod or go.sum is not tidy, run 'go mod tidy'
Execute go mod tidy locally and commit the resulting changes (likely including an updated go.sum) to restore reproducible builds and unblock CI.
🤖 Prompt for AI Agents
In go.mod around lines 5 to 9, the module dependencies are not tidy, causing CI
failures. Run the command 'go mod tidy' locally to clean up and update both
go.mod and go.sum files with any new or removed dependencies. After running the
command, commit the updated go.mod and go.sum files to ensure the module is tidy
and the CI pipeline passes.
Bumps github.com/mark3labs/mcp-go from 0.25.0 to 0.33.0.
Release notes
Sourced from github.com/mark3labs/mcp-go's releases.
... (truncated)
Commits
6a54215Implement sampling in Stdio (#461)656a7b4Support creating anStdioclient with options (#457)01e802fFix unused import in readme example (#469)d0fa06eAdd support for MCP host session management (#466)251da13feature: add support ResourceTemplates to mcptest package (#449)1eddde7feat: client-side streamable-http transport supports continuously listening ...8f5b048Fix docs (#430)0fdb197feat: add ResourceLink type and parsing support (#407)d807ae7fix(client/transport/stream): check for nil pointer (#404)93176e8fixed nil error (#406)Dependabot 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 #23
Summary by CodeRabbit
Completed by Agent
Fixes #24