home / skills / jeremylongshore / claude-code-plugins-plus-skills / groq-upgrade-migration
This skill guides upgrading Groq SDKs, detects breaking changes, and harmonizes code with new API versions for safer migrations.
npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill groq-upgrade-migrationReview the files below or copy the command above to add this skill to your agents.
---
name: groq-upgrade-migration
description: |
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".
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(git:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---
# 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
```bash
npm list @groq/sdk
npm view @groq/sdk version
```
### Step 2: Review Changelog
```bash
open https://github.com/groq/sdk/releases
```
### Step 3: Create Upgrade Branch
```bash
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
```typescript
// Before (v1.x)
import { Client } from '@groq/sdk';
// After (v2.x)
import { GroqClient } from '@groq/sdk';
```
### Configuration Changes
```typescript
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new GroqClient({
apiKey: 'xxx',
});
```
### Rollback Procedure
```bash
npm install @groq/[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('[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
- [Groq Changelog](https://github.com/groq/sdk/releases)
- [Groq Migration Guide](https://docs.groq.com/migration)
## Next Steps
For CI integration during upgrades, see `groq-ci-integration`.This skill analyzes, plans, and executes Groq SDK upgrades with automated detection of breaking changes and deprecations. It guides repository preparation, changelog review, code updates, testing, and rollback so upgrades complete with minimal risk. Use it to move between Groq SDK major or minor versions and to validate API compatibility across environments.
The skill inspects the installed @groq/sdk version, fetches release notes, and compares known breaking changes against your codebase. It generates a migration plan that lists import and configuration updates, runs tests in a branch, and applies or suggests automated code edits. It also produces rollback steps and captures deprecation warnings for ongoing monitoring.
How do I detect breaking changes before upgrading?
Compare your current version to the target release notes and run a code search for renamed imports, method names, and changed configuration keys.
What if tests fail after installing the new SDK?
Revert to the upgrade branch, review failing test traces for API mismatches, apply code changes for renamed methods or parameters, then re-run tests. Use the documented rollback command if immediate revert is required.