Repository navigation
Conversation
Issue GoogleCloudPlatform#1588 asks for two things: (1) documentation + sample-config reference swaps imagen -> nanobanana/gemini, and (2) an audit of any remaining imagen references. The content changes of commit dc48d1f (closed draft PR GoogleCloudPlatform#1245) are already present on main: cherry-picking it onto main conflicts only on context drift in four files, and resolving those by keeping main's version yields a zero net diff. This PR closes the loop on (2) and frames the open decision the issue explicitly raises. Changes (documentation only, no code changes): - mcp-imagen-go/README.md: add a deprecation banner at the top pointing users at mcp-nanobanana-go / mcp-gemini-go and at the new DEPRECATION.md. - mcp-imagen-go/DEPRECATION.md: full audit of remaining mcp-imagen-go / imagen_t2i references, split into the in-tree sweep (experiments/mcp-genmedia/, all hits acceptable) and a repo-wide sweep that flags the hand-maintained docs-site pages still routing new users to mcp-imagen-go (candidates for cleanup, offered as follow-up work), plus the CI entries that still build and publish the server. The DEPRECATION.md also frames the issue's open decision (references-only vs. remove the server directory): it cites the maintainer's 2026-08-22 inventory comment and the same-day correction verifying that the upscale and VTO surfaces do have practical Nano Banana approximations that are not drop-in replacements, and recommends keeping the directory in-tree until the maintainer decides on the migration path. Either way, removal is a single mechanical follow-up PR. References GoogleCloudPlatform#1588.
This was referenced Oct 17, 2026
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
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.
What
Closes the documentation scope of issue #1588 by:
mcp-imagen-go/README.mdpointing users at
mcp-nanobanana-go/mcp-gemini-go.mcp-imagen-go/DEPRECATION.mdwith the full audit of remainingmcp-imagen-go/imagen_t2ireferences — in-tree(
experiments/mcp-genmedia/) and repo-wide — each hit classified, theframed open decision the issue raises, and re-runnable grep commands.
Documentation-only, no code changes. References #1588.
What's already landed
The content changes of commit
dc48d1f6(the one relevant commit carriedby the closed draft PR #1245) are already present on
main: the samplegemini-extension.jsonfiles andsample_settings.json, theinstall.sh/deploy-cloudrun.shexclusions, and the genkit/adk sampleupdates. I verified this by cherry-picking
dc48d1f6onto currentmain— it conflicts in four files purely on context drift, and resolving those
by keeping main's version yields a zero net diff.
Audit conclusion
experiments/mcp-genmedia/: no stale user-facing referencesremain. Every hit is the enforcement itself, an immutable changelog
entry, an in-tree implementation/build file, or a historical/comparison
comment (DEPRECATION.md §3, 21 rows).
routes new users to
mcp-imagen-goin three places (an ADK setupinstruction, a Gemini-CLI example settings block registering an
"imagen"server, and a generic run example), and the publishedmcp-imagen-gopage has no deprecation notice. I flagged those ascandidates for cleanup — happy to follow up with that docs-site swap
PR, of the same kind
dc48d1f6already did in-tree. Two CI entries(build loop + publish matrix) still include
mcp-imagen-go; consistentwhile the directory stays, and they should travel with the removal PR
whenever the directory goes.
Open decision
Issue #1588 asks whether to keep references-only deprecation or also
remove the
mcp-imagen-godirectory. Per the 2026-08-22 inventorycomment and the same-day correction on #1588 (verified live on Vertex AI
with
gemini-3.1-flash-image), the core-app/imagen-upscaleandVirtual Try-On surfaces do have practical Nano Banana approximations,
but they are not drop-in replacements (upscale is a re-generation, not a
faithful super-resolution; VTO is not catalog-grade).
DEPRECATION.md§4therefore recommends keeping the directory in-tree until you decide
whether those approximations are acceptable; the removal, when agreed,
is a single mechanical follow-up PR, and the audit lists everything that
would need to travel with it.
How to verify
Each hit should match a row in DEPRECATION.md §3 / §3.1. (Note: use GNU
grep; ripgrep users need
--no-ignorebecause the repo's.gitignorerule
**/mcp-*-go/mcp-*-gohides those tracked files.)Notes
and/or (b) the directory-removal PR once the upscale/VTO migration
path is agreed.
References #1588.