perplexity-upgrade-migration
Analyze, plan, and execute Perplexity SDK upgrades with breaking change detection.Use when upgrading Perplexity SDK versions, detecting deprecations,or migrating to new API versions.Trigger with phrases like "upgrade perplexity", "perplexity migration","perplexity breaking changes", "update perplexity SDK", "analyze perplexity version".
When & Why to Use This Skill
The Perplexity Upgrade & Migration skill is a specialized developer utility designed to automate the complex process of SDK version management. It streamlines the transition between Perplexity SDK versions by intelligently detecting breaking changes, refactoring deprecated code patterns, and managing dependency updates. By integrating with Git and npm, it ensures that migrations are performed safely in isolated branches with automated testing and documented rollback procedures, significantly reducing technical debt and manual refactoring time.
Use Cases
- Case 1: Automated Migration - Seamlessly upgrading from Perplexity SDK v1.x to v2.x by automatically refactoring 'Client' imports to 'PerplexityClient' and updating configuration objects to match new API schemas.
- Case 2: Breaking Change Detection - Analyzing existing codebases to identify deprecated method signatures or changed parameters before a major version release to prevent production runtime errors.
- Case 3: Dependency Lifecycle Management - Using automated workflows to check for the latest SDK versions, review changelogs, and initialize dedicated upgrade branches with updated npm packages.
- Case 4: Environment Validation - Executing test suites post-upgrade and monitoring for Deprecation Warnings in development environments to ensure proactive maintenance of AI integrations.
| name | perplexity-upgrade-migration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Perplexity Upgrade & Migration
Overview
Guide for upgrading Perplexity SDK versions and handling breaking changes.
Prerequisites
- Current Perplexity SDK installed
- Git for version control
- Test suite available
- Staging environment
Instructions
Step 1: Check Current Version
npm list @perplexity/sdk
npm view @perplexity/sdk version
Step 2: Review Changelog
open https://github.com/perplexity/sdk/releases
Step 3: Create Upgrade Branch
git checkout -b upgrade/perplexity-sdk-vX.Y.Z
npm install @perplexity/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 '@perplexity/sdk';
// After (v2.x)
import { PerplexityClient } from '@perplexity/sdk';
Configuration Changes
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new PerplexityClient({
apiKey: 'xxx',
});
Rollback Procedure
npm install @perplexity/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('[Perplexity]', 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 perplexity-ci-integration.