executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
posthog-upgrade-migrationAnalyze, plan, and execute PostHog SDK upgrades with breaking change detection. Use when upgrading PostHog SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade posthog", "posthog migration", "posthog breaking changes", "update posthog SDK", "analyze posthog version".
Independent GitHub snapshot · Automated classification · Original documentation governs
Guide for upgrading PostHog SDK versions and handling breaking changes.
npm list @posthog/sdk
npm view @posthog/sdk version
open https://github.com/posthog/sdk/releases
git checkout -b upgrade/posthog-sdk-vX.Y.Z
npm install @posthog/sdk@latest
npm test
Update import statements, configuration, and method signatures as needed.
| 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 |
// Before (v1.x)
import { Client } from '@posthog/sdk';
// After (v2.x)
import { PostHogClient } from '@posthog/sdk';
// Before (v1.x)
const client = new Client({ key: 'xxx' });
// After (v2.x)
const client = new PostHogClient({
apiKey: 'xxx',
});
npm install @posthog/sdk@1.x.x --save-exact
// Monitor for deprecation warnings in development
if (process.env.NODE_ENV === 'development') {
process.on('warning', (warning) => {
if (warning.name === 'DeprecationWarning') {
console.warn('[PostHog]', 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
For CI integration during upgrades, see posthog-ci-integration.