nano-banana-pro: respect explicit --resolution when editing images#36880
Conversation
Greptile SummaryThis PR fixes a long-standing bug in Key changes:
Confidence Score: 4/5
Last reviewed commit: 21b1d59 |
f15fc35 to
0d7b2ef
Compare
|
Cleaned this branch up and pushed it back to the PR head. The active diff is now just the Nano Banana resolution fix plus the changelog entry on top of current Keeping #36881 open as the canonical issue until this lands. If you spot any remaining scope drift, call it out and I’ll recheck it quickly. |
* main: Mattermost: harden interaction callback binding (openclaw#38057) WhatsApp: honor outbound mediaMaxMb (openclaw#38097) openai-image-gen: validate --background and --style options (openclaw#36762) Docs: align BlueBubbles media cap wording Telegram/Discord: honor outbound mediaMaxMb uploads (openclaw#38065) CI: run changed-scope on main pushes Skills/nano-banana-pro: clarify MEDIA token comment (openclaw#38063) nano-banana-pro: respect explicit --resolution when editing images (openclaw#36880) CI: drop unused install-smoke bootstrap fix(nano-banana-pro): remove space after MEDIA: token in generate_image.py (openclaw#18706) docs: context engine docs(config): list the context engine plugin slot docs(plugins): add context-engine manifest kind example docs(plugins): document context engine slots and registration docs(protocol): document slash-delimited schema lookup plugin ids docs(tools): document slash-delimited config schema lookup paths fix(session): tighten direct-session webchat routing matching (openclaw#37867) feature(context): extend plugin system to support custom context management (openclaw#22201) Gateway: allow slash-delimited schema lookup paths
…penclaw#36880) * nano-banana-pro: respect explicit --resolution when editing images * Changelog: note nano banana resolution fix * Update CHANGELOG.md --------- Co-authored-by: Vincent Koc <[email protected]>
…penclaw#36880) * nano-banana-pro: respect explicit --resolution when editing images * Changelog: note nano banana resolution fix * Update CHANGELOG.md --------- Co-authored-by: Vincent Koc <[email protected]>
…penclaw#36880) * nano-banana-pro: respect explicit --resolution when editing images * Changelog: note nano banana resolution fix * Update CHANGELOG.md --------- Co-authored-by: Vincent Koc <[email protected]>
…penclaw#36880) * nano-banana-pro: respect explicit --resolution when editing images * Changelog: note nano banana resolution fix * Update CHANGELOG.md --------- Co-authored-by: Vincent Koc <[email protected]>
…penclaw#36880) * nano-banana-pro: respect explicit --resolution when editing images * Changelog: note nano banana resolution fix * Update CHANGELOG.md --------- Co-authored-by: Vincent Koc <[email protected]>
…penclaw#36880) Co-authored-by: Vincent Koc <[email protected]> (cherry picked from commit 37a3fb0)
…penclaw#36880) Co-authored-by: Vincent Koc <[email protected]> (cherry picked from commit 37a3fb0)
What changed
skills/nano-banana-pro/scripts/generate_image.pyso--resolutionis only auto-detected when the flag is omitted.auto_detect_resolutionandchoose_output_resolutionhelpers to make resolution behavior explicit and testable.skills/nano-banana-pro/scripts/test_generate_image.pycovering:--resolutionwith input images--resolution 1Kwith large input imagesWhy
--resolutionis not explicitly provided.--resolution 1Kwas indistinguishable from the default, so large input images could still be auto-upgraded to 2K/4K.Testing
source .venv/bin/activate && pytest -q