vastai-upgrade-migration
Analyze, plan, and execute Vast.ai SDK upgrades with breaking change detection.Use when upgrading Vast.ai SDK versions, detecting deprecations,or migrating to new API versions.Trigger with phrases like "upgrade vastai", "vastai migration","vastai breaking changes", "update vastai SDK", "analyze vastai version".
When & Why to Use This Skill
This Claude skill automates the analysis, planning, and execution of Vast.ai SDK upgrades. It streamlines the migration process by detecting breaking changes, identifying deprecated APIs, and refactoring code to ensure compatibility with the latest Vast.ai versions, significantly reducing manual maintenance effort and technical debt.
Use Cases
- Major Version Migration: Seamlessly transition from older Vast.ai SDK versions (e.g., v1.x to v2.x) by automatically updating import statements and configuration patterns.
- Breaking Change Detection: Scan existing codebases to identify and fix method signatures or parameters that are no longer supported in newer SDK releases.
- Deprecation Monitoring: Proactively identify deprecated features in development environments and replace them with modern alternatives to prevent future system failures.
- Automated Upgrade Planning: Generate comprehensive upgrade checklists, including git branch creation, dependency updates, and test suite execution for SDK maintenance.
| name | vastai-upgrade-migration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(git:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Vast.ai Upgrade & Migration
Overview
Guide for upgrading Vast.ai SDK versions and handling breaking changes.
Prerequisites
- Current Vast.ai SDK installed
- Git for version control
- Test suite available
- Staging environment
Instructions
Step 1: Check Current Version
npm list @vastai/sdk
npm view @vastai/sdk version
Step 2: Review Changelog
open https://github.com/vastai/sdk/releases
Step 3: Create Upgrade Branch
git checkout -b upgrade/vastai-sdk-vX.Y.Z
npm install @vastai/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 '@vastai/sdk';
// After (v2.x)
import { Vast.aiClient } from '@vastai/sdk';
Configuration Changes
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new Vast.aiClient({
apiKey: 'xxx',
});
Rollback Procedure
npm install @vastai/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('[Vast.ai]', 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 vastai-ci-integration.