Skip to content

doc: deprecate legacy genai-toolbox strings in java sdk ecosystem#60

Open
anubhav756 wants to merge 2 commits intomainfrom
anubhav-doc
Open

doc: deprecate legacy genai-toolbox strings in java sdk ecosystem#60
anubhav756 wants to merge 2 commits intomainfrom
anubhav-doc

Conversation

@anubhav756
Copy link
Copy Markdown
Contributor

@anubhav756 anubhav756 commented Apr 16, 2026

Refactors documentation pages, .github issue and renovate templates, and integration test setups across the mcp-toolbox-sdk-java module stack to align with the global mcp-toolbox taxonomy. Standardizes remote resource links onto the new mcp-toolbox-for-databases pipeline block natively.

@anubhav756 anubhav756 self-assigned this Apr 16, 2026
@anubhav756 anubhav756 requested a review from a team as a code owner April 16, 2026 13:54
label: MCP Toolbox version
description: |
What version of MCP Toolbox are you using (`toolbox --version`)? e.g.
- toolbox version 0.3.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • [SUGGESTION] .github/ISSUE_TEMPLATE/bug_report.yml:47-49
    • Observation: The example versions in the "MCP Toolbox version" field description still reference 0.3.0 (e.g., toolbox version 0.3.0 and ...toolbox:0.3.0).
    • Suggestion: Update these example strings to 1.1.0 to maintain consistency with the version bump performed in the rest of the PR (e.g., in demo-applications/cymbal-transit/README.md).

Comment thread demo-applications/cymbal-transit/README.md
Comment thread example/README.md
In any case remember to change the `YOUR_TOOLBOX_SERVICE_ENDPOINT` placeholder in the respective files.

If you decide to deploy your toolbox endpoint in cloud run, here's how you can do it: https://googleapis.github.io/genai-toolbox/how-to/deploy_toolbox
If you decide to deploy your toolbox endpoint in cloud run, here's how you can do it: https://mcp-toolbox.dev/documentation/deploy-to/
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you decide to deploy your toolbox endpoint in cloud run, here's how you can do it: https://mcp-toolbox.dev/documentation/deploy-to/
If you decide to deploy your toolbox endpoint in cloud run, here's how you can do it: https://mcp-toolbox.dev/documentation/deploy-to/cloud-run/

@stenalpjolly
Copy link
Copy Markdown

Issues Found

  • [MUST FIX] AGENTS.md:49
    • Observation: The local test execution instructions still hardcode TOOLBOX_VERSION=0.26.0. Since the PR updates ToolboxE2ESetup.java to fetch from the new mcp-toolbox-for-databases bucket (which does not contain the legacy v0.26.0 binaries), local E2E tests will fail with a 404 for any developer using this command snippet.
    • Suggestion: Update TOOLBOX_VERSION=0.26.0 to TOOLBOX_VERSION=1.1.0 to match the version bump applied to integration.cloudbuild.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants