home / skills / jeremylongshore / claude-code-plugins-plus-skills / ideogram-upgrade-migration

This skill analyzes Ideogram SDK upgrades, detects breaking changes, and guides implementation to ensure smooth migration and tests.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-upgrade-migration

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
name: ideogram-upgrade-migration
description: |
  Analyze, plan, and execute Ideogram SDK upgrades with breaking change detection.
  Use when upgrading Ideogram SDK versions, detecting deprecations,
  or migrating to new API versions.
  Trigger with phrases like "upgrade ideogram", "ideogram migration",
  "ideogram breaking changes", "update ideogram SDK", "analyze ideogram version".
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(git:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Ideogram Upgrade & Migration

## Overview
Guide for upgrading Ideogram SDK versions and handling breaking changes.

## Prerequisites
- Current Ideogram SDK installed
- Git for version control
- Test suite available
- Staging environment

## Instructions

### Step 1: Check Current Version
```bash
npm list @ideogram/sdk
npm view @ideogram/sdk version
```

### Step 2: Review Changelog
```bash
open https://github.com/ideogram/sdk/releases
```

### Step 3: Create Upgrade Branch
```bash
git checkout -b upgrade/ideogram-sdk-vX.Y.Z
npm install @ideogram/sdk@latest
npm test
```

### Step 4: Handle Breaking Changes
Update import statements, configuration, and method signatures as needed.

## Output
- Updated SDK version
- Fixed breaking changes
- Passing test suite
- Documented rollback procedure

## Error Handling
| SDK Version | API Version | Node.js | Breaking Changes |
|-------------|-------------|---------|------------------|
| 3.x | 2024-01 | 18+ | Major refactor |
| 2.x | 2023-06 | 16+ | Auth changes |
| 1.x | 2022-01 | 14+ | Initial release |

## Examples

### Import Changes
```typescript
// Before (v1.x)
import { Client } from '@ideogram/sdk';

// After (v2.x)
import { IdeogramClient } from '@ideogram/sdk';
```

### Configuration Changes
```typescript
// Before (v1.x)
const client = new Client({ key: 'xxx' });

// After (v2.x)
const client = new IdeogramClient({
  apiKey: 'xxx',
});
```

### Rollback Procedure
```bash
npm install @ideogram/[email protected] --save-exact
```

### Deprecation Handling
```typescript
// Monitor for deprecation warnings in development
if (process.env.NODE_ENV === 'development') {
  process.on('warning', (warning) => {
    if (warning.name === 'DeprecationWarning') {
      console.warn('[Ideogram]', warning.message);
      // Log to tracking system for proactive updates
    }
  });
}

// Common deprecation patterns to watch for:
// - Renamed methods: client.oldMethod() -> client.newMethod()
// - Changed parameters: { key: 'x' } -> { apiKey: 'x' }
// - Removed features: Check release notes before upgrading
```

## Resources
- [Ideogram Changelog](https://github.com/ideogram/sdk/releases)
- [Ideogram Migration Guide](https://docs.ideogram.com/migration)

## Next Steps
For CI integration during upgrades, see `ideogram-ci-integration`.

Overview

This skill analyzes, plans, and executes Ideogram SDK upgrades while detecting breaking changes and deprecations. It guides developers through version checks, changelog review, code adjustments, testing, and rollback procedures to keep projects working after an SDK update. The goal is a predictable, test-driven migration with minimal downtime.

How this skill works

The skill inspects the current installed Ideogram SDK version, compares it to target releases, and scans code for common breaking-change patterns (imports, constructor options, renamed methods). It produces a migration plan with branch and test instructions, automated update commands, and suggested code edits. It flags deprecations and provides rollback commands and testing checkpoints for staging and CI.

When to use it

  • When preparing to upgrade @ideogram/sdk to a newer major or minor version
  • When CI or local tests reveal deprecation warnings tied to Ideogram
  • Before merging an SDK upgrade into main or production branches
  • When migrating code to new API shapes (imports, client constructors, method names)
  • When validating Node.js runtime compatibility with a target SDK version

Best practices

  • Run npm list and npm view to confirm installed and published versions before starting
  • Create a dedicated upgrade branch and install the target SDK there to isolate changes
  • Review the package changelog and release notes for breaking changes and migration hints
  • Run the full test suite in a staging environment and add deprecation logging during development
  • Document rollback steps and pin exact package versions in package.json if stability is required

Example use cases

  • Upgrade from 2.x to 3.x which includes a major refactor that changes client names and APIs
  • Adjust import statements and constructor options after a rename: Client -> IdeogramClient and key -> apiKey
  • Add automated deprecation warning capture in development to surface upcoming removals
  • Integrate SDK upgrade into CI: run install, tests, and lint on an upgrade branch before merge
  • Perform a quick rollback to a known-good patch version when a production bug is discovered

FAQ

What are the first commands to run when starting an Ideogram upgrade?

Check the local and remote versions with npm list @ideogram/sdk and npm view @ideogram/sdk version, then create an upgrade branch and install the target version.

How do I detect breaking changes in my codebase?

Search for renamed imports and methods, compare constructor/config shapes, run the test suite, and watch development deprecation warnings to identify affected areas.