groq-upgrade-migration
Analyze, plan, and execute Groq SDK upgrades with breaking change detection.Use when upgrading Groq SDK versions, detecting deprecations,or migrating to new API versions.Trigger with phrases like "upgrade groq", "groq migration","groq breaking changes", "update groq SDK", "analyze groq version".
When & Why to Use This Skill
This Claude skill automates the complex process of upgrading Groq SDKs by identifying breaking changes, managing version migrations, and refactoring codebases. It streamlines dependency management, ensures compatibility with the latest Groq API versions, and provides structured rollback procedures to maintain development stability and minimize downtime.
Use Cases
- Migrating legacy Groq SDK implementations (e.g., v1.x to v2.x) by automatically updating import statements and configuration objects to match new API signatures.
- Proactively detecting and resolving deprecation warnings in development environments to prevent future breaking changes from impacting production systems.
- Automating the end-to-end upgrade workflow, including branch creation, dependency installation, and running test suites to validate SDK compatibility.
- Analyzing changelogs and release notes to plan technical debt reduction strategies related to Groq integration.
| name | groq-upgrade-migration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Groq Upgrade & Migration
Overview
Guide for upgrading Groq SDK versions and handling breaking changes.
Prerequisites
- Current Groq SDK installed
- Git for version control
- Test suite available
- Staging environment
Instructions
Step 1: Check Current Version
npm list @groq/sdk
npm view @groq/sdk version
Step 2: Review Changelog
open https://github.com/groq/sdk/releases
Step 3: Create Upgrade Branch
git checkout -b upgrade/groq-sdk-vX.Y.Z
npm install @groq/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
// Before (v1.x)
import { Client } from '@groq/sdk';
// After (v2.x)
import { GroqClient } from '@groq/sdk';
Configuration Changes
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new GroqClient({
apiKey: 'xxx',
});
Rollback Procedure
npm install @groq/sdk@1.x.x --save-exact
Deprecation Handling
// Monitor for deprecation warnings in development
if (process.env.NODE_ENV === 'development') {
process.on('warning', (warning) => {
if (warning.name === 'DeprecationWarning') {
console.warn('[Groq]', 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
Next Steps
For CI integration during upgrades, see groq-ci-integration.