Repository navigation
Expose Nano Banana 2.1 in image MCP tools - #968
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope and dependency
Add base
nano-banana-2.1to the dedicated Nano Banana and OpenAI image MCP model types and tool descriptions. The dedicated tool documents 1K/2K/4K; no:officialvariant is offered.Depends on both upstream release PRs:
Runtime: https://github.com/AceDataCloud/PlatformService/pull/2565
Billing and API contract: https://github.com/AceDataCloud/PlatformBackend/pull/2148
Validation
Nano Banana MCP: 19 tests passed, 2 skipped. OpenAI MCP: 77 tests passed. Focused Ruff passed;
git diff --checkpassed. Strict mypy could not run locally because the package registry was unreachable and mypy was not cached; CI remains the gate.Rollout and rollback
Merge/publish only after the paid public API and model catalog are live. The monorepo sync/publish workflow owns standalone packages. Roll back by removing the model from the two Literals and descriptions, then republishing.
Adversarial review: not requested.