infer-upgrade
Infer Upgrade
Updates all three Infer components to their latest versions.
Step 1: Check current vs latest
Run these commands to detect what's installed and what's available:
# Latest versions on npm
echo "SDK_LATEST=$(npm view @inferevents/sdk version 2>/dev/null || echo 'not-published')"
echo "MCP_LATEST=$(npm view @inferevents/mcp version 2>/dev/null || echo 'not-published')"
# Installed SDK in current project
echo "SDK_INSTALLED=$(node -e "try{console.log(require('@inferevents/sdk/package.json').version)}catch{console.log('not-installed')}" 2>/dev/null || echo 'not-installed')"
# Check if MCP config exists
echo "MCP_CONFIG=$(cat ~/.infer/config.json 2>/dev/null | head -1 || echo 'no-config')"
More from infer-events/skills
infer-insights
Use when the user asks for LLM observability insights, a health check, a pulse on their agent, or says "what should I know about my data." Also use when invoked via /schedule or /loop for automated daily insights.
20infer-tracking-plan
Use when the user wants to ADD NEW tracking events to their codebase, needs a tracking plan, or after installing the Infer SDK. Triggers on "what should I track", "suggest events", "tracking plan", "add tracking". Do NOT use for checking live data or querying existing events — use the get_top_events MCP tool for that.
20infer-setup
Use when setting up Infer analytics in a new project, integrating the SDK, or configuring the MCP server. Triggers on "set up analytics", "add tracking", "integrate infer", "install infer", or when a project has no analytics and the user wants to add it.
19infer-analytics
Use when the user asks questions about their analytics data, event counts, retention, user journeys, or funnels. Teaches agents how to interpret Infer MCP tool results.
12