replit-upgrade-migration
Analyze, plan, and execute Replit SDK upgrades with breaking change detection.Use when upgrading Replit SDK versions, detecting deprecations,or migrating to new API versions.Trigger with phrases like "upgrade replit", "replit migration","replit breaking changes", "update replit SDK", "analyze replit version".
When & Why to Use This Skill
This Claude skill automates the analysis, planning, and execution of Replit SDK upgrades. It specializes in detecting breaking changes and deprecations, streamlining the migration process to newer API versions through automated environment checks, branch management, and code refactoring guidance to ensure project stability.
Use Cases
- Upgrading legacy Replit SDK versions (e.g., v1.x to v2.x) while automatically refactoring import statements and configuration objects.
- Proactively identifying and resolving deprecation warnings in development environments to prevent future breaking changes in production.
- Automating the migration workflow, including version verification, changelog review, and creating dedicated upgrade branches with Git.
- Ensuring system stability during upgrades by executing test suites and providing documented rollback procedures for failed migrations.
| name | replit-upgrade-migration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Replit Upgrade & Migration
Overview
Guide for upgrading Replit SDK versions and handling breaking changes.
Prerequisites
- Current Replit SDK installed
- Git for version control
- Test suite available
- Staging environment
Instructions
Step 1: Check Current Version
npm list @replit/sdk
npm view @replit/sdk version
Step 2: Review Changelog
open https://github.com/replit/sdk/releases
Step 3: Create Upgrade Branch
git checkout -b upgrade/replit-sdk-vX.Y.Z
npm install @replit/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 '@replit/sdk';
// After (v2.x)
import { ReplitClient } from '@replit/sdk';
Configuration Changes
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new ReplitClient({
apiKey: 'xxx',
});
Rollback Procedure
npm install @replit/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('[Replit]', 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 replit-ci-integration.