Nano Banana Image Editor Plugin Upgrade

Nano Banana Image Editor Plugin Upgrade

You are running the nano-banana-image-editor upgrade command to update the plugin to the latest version.

Your Task

Guide the user through upgrading the nano-banana-image-editor plugin by pulling the latest changes from the marketplace repository.

Workflow

Step 1: Verify Current Installation

Check the current version and installation location:

# Get marketplace directory
MARKETPLACE_DIR=$(dirname $(dirname ${CLAUDE_PLUGIN_ROOT}))

# Get current version from marketplace.json
CURRENT_VERSION=$(jq -r '.plugins[] | select(.name=="nano-banana-image-editor") | .version' "$MARKETPLACE_DIR/.claude-plugin/marketplace.json")

# Verify git repository
cd "$MARKETPLACE_DIR" && git rev-parse --git-dir >/dev/null 2>&1 && echo "✓ Git repository found" || echo "✗ Not a git repository"

Output to user:

Current version: [version]
Marketplace directory: [path]

Step 2: Check for Updates

Fetch the latest tags and check for updates:

cd "$MARKETPLACE_DIR"
git fetch --tags origin

Then get the version information:

# Get the latest version tag for this plugin
LATEST_TAG=$(git tag -l 'nano-banana-image-editor/v*' --sort=-v:refname | head -n 1)

# Get current tag (if on a tag)
CURRENT_TAG=$(git describe --tags --exact-match 2>/dev/null || echo "none")

# Filter to only nano-banana-image-editor tags if we're on a tag
if [ "$CURRENT_TAG" != "none" ]; then
  echo "$CURRENT_TAG" | grep -q '^nano-banana-image-editor/' || CURRENT_TAG="none"
fi

echo "Latest tag: $LATEST_TAG"
echo "Current tag: $CURRENT_TAG"

Analyze the output:

• If LATEST_TAG is empty → No tagged releases available yet
• If CURRENT_TAG equals LATEST_TAG → Already on latest version
• If LATEST_TAG is newer → Continue to Step 3
• If git fetch fails → Inform user there's a connection issue

Output to user:

Current version: [CURRENT_VERSION] (tag: [CURRENT_TAG or "not on a tagged release"])
Latest available: [LATEST_TAG]

Step 3: Show Release Notes

If updates are available, show what's changed by reading the CHANGELOG:

cd "$MARKETPLACE_DIR" && git show "$LATEST_TAG:plugins/nano-banana-image-editor/CHANGELOG.md" | head -50

Present the release notes to the user, focusing on the latest version's changes.

Step 4: Confirm Upgrade

Use the AskUserQuestion tool to ask:

• Question: "Ready to upgrade nano-banana-image-editor to the latest version?"
• Options:
  • "Yes, upgrade now" (description: "Pull latest changes from the repository")
  • "No, not now" (description: "Keep current version")

If user selects "No, not now":

• Output: "Upgrade cancelled. Your current version remains unchanged."
• Exit the command

Step 5: Perform Upgrade

If user confirms, checkout the latest tagged release:

cd "$MARKETPLACE_DIR" && git checkout "$LATEST_TAG"

Check the exit code:

• Exit code 0 → Success, continue to Step 6
• Exit code != 0 → Error occurred, show user the error message and stop

Note: This checks out the specific tagged release ensuring you get a stable, tested version.

Step 6: Rebuild Plugin Dependencies

After pulling changes, reinstall Python dependencies:

cd ${CLAUDE_PLUGIN_ROOT}/skills/nano-banana-image-editor && bash scripts/install_dependencies.sh

Monitor for errors:

• If successful → Continue to Step 7
• If errors occur → Show errors to user and explain that manual intervention may be needed

Step 7: Verify New Version

Check the updated version:

NEW_VERSION=$(jq -r '.plugins[] | select(.name=="nano-banana-image-editor") | .version' "$MARKETPLACE_DIR/.claude-plugin/marketplace.json")

Step 8: Success Message & Restart Prompt

Output to user:

✅ Nano Banana Image Editor upgraded successfully!

Previous version: [old version]
Current version: [new version]

⚠️  Important: You must restart Claude Code to apply the changes.

To restart:
1. Close this conversation
2. Restart Claude Code
3. Start a new session

After restarting, you can verify the upgrade by running:
/nano-banana-image-editor:image test

Error Handling

Git Repository Not Found

If the marketplace directory is not a git repository:

❌ Upgrade failed: nano-banana-image-editor marketplace is not a git repository.

This can happen if the plugin was installed differently. To upgrade manually:

1. Navigate to: [marketplace directory]
2. Run: git fetch --tags origin
3. List tags: git tag -l 'nano-banana-image-editor/v*' --sort=-v:refname
4. Checkout latest: git checkout <latest-version-tag>
5. Navigate to: [plugin directory]/skills/nano-banana-image-editor
6. Run: bash scripts/install_dependencies.sh
7. Restart Claude Code

If you continue to have issues, try reinstalling the plugin:
/plugin marketplace remove emdashcodes-claude-code-plugins
/plugin marketplace add emdashcodes/claude-code-plugins
/plugin install nano-banana-image-editor@emdashcodes-claude-code-plugins

Network/Connection Errors

If git fetch/pull fails due to network issues:

❌ Upgrade failed: Unable to connect to repository.

Please check your network connection and GitHub access.

To upgrade manually:
cd [marketplace directory]
git fetch --tags origin
git tag -l 'nano-banana-image-editor/v*' --sort=-v:refname  # List versions
git checkout <latest-version-tag>
cd [plugin directory]/skills/nano-banana-image-editor
bash scripts/install_dependencies.sh

Then restart Claude Code.

Build Errors

If dependency installation fails:

❌ Upgrade completed but dependency installation failed.

The latest code was pulled, but there were errors during Python dependency installation.
You may need to troubleshoot manually.

Error details:
[show error output]

To retry manually:
cd [plugin directory]/skills/nano-banana-image-editor
bash scripts/install_dependencies.sh

If issues persist, report at: https://github.com/emdashcodes/claude-code-plugins/issues

Important Notes

• This command upgrades to the latest tagged release (stable, tested versions)
• Uses plugin-prefixed semantic versioning tags (e.g., nano-banana-image-editor/v1.0.0, nano-banana-image-editor/v1.1.0)
• Your configuration file (.nano-banana-config.json) will not be affected
• A restart of Claude Code is required for changes to take effect
• The upgrade process does not modify your existing Gemini API token or settings