{"uid":"cap_fIjffVwvWxJ4gTZomxVvh","slug":"dependency-upgrade-plan-multi-package-e8228052","name":"Dependency Upgrade Plan (Multi-Package)","description":"Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk score, ordered by risk, plus peer requirements between the listed packages.","url":"https://upgrade-brief.shopttyass-85f.workers.dev/mcp?utm_source=zero.xyz#dependency_upgrade_plan","method":"POST","headers":{},"bodySchema":null,"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.02","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"registry","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.02/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.02","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.02","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_0rCe0KruQU9J3Ft8Ae6VK","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.02","costPer":"request","priority":0,"asset":null,"unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Generates a consolidated upgrade plan for up to 5 npm or PyPI packages, including breaking changes, major bumps, engine/peer dependency changes, migration guides, risk scores ordered by risk, and cross-package peer requirements.","exampleAgentPrompt":"Can you give me a full upgrade plan for react (17 to 18), react-dom (17 to 18), and next (12 to 13) — I want to see breaking changes, migration guides, and which one is riskiest to upgrade first?","exampleUseCases":[{"title":"React ecosystem upgrade risk assessment","prompt":"I'm planning to upgrade react, react-dom, and react-router-dom all at once — can you generate an upgrade plan from their current versions to latest, show me the breaking changes and migration steps, and tell me which order I should upgrade them in based on risk?"},{"title":"Python data stack upgrade plan","prompt":"I need to upgrade numpy, pandas, and scikit-learn in my ML project — can you give me a combined upgrade plan showing breaking changes, Python version requirements, peer dependency conflicts between them, and a risk score for each?"},{"title":"Pre-release CI upgrade gate","prompt":"Before our next release we're bumping express from 4 to 5, lodash from 4.17 to 4.17.21, and axios from 0.27 to 1.6 — can you pull together a single upgrade brief showing what breaks, what migration steps we need, and rank the packages by how risky the upgrade is?"}],"resultDescription":"A structured upgrade plan covering up to 5 packages: for each package, the documented breaking changes to the target version, all major version bumps in the range, engine or Python version requirement changes, peer dependency changes, a migration guide, and a numeric risk score. The packages are ordered from highest to lowest risk. Additionally, peer dependency conflicts or requirements between the listed packages themselves are surfaced.","failureModes":["Package name not found on npm or PyPI — returns an error for that package","Version range invalid or target version does not exist — error for that package entry","More than 5 packages submitted — request rejected or truncated","No breaking changes documented for a package — returns empty section for that field","Network timeout fetching registry metadata for one or more packages","Unsupported ecosystem specified (neither npm nor PyPI)"],"whenToPreferThis":"Use this endpoint when you need to plan upgrades for multiple npm or PyPI packages in a single call and want a unified risk-ranked view with cross-package peer dependency analysis. Prefer it over single-package endpoints when coordinating a batch upgrade across a project's dependency tree, especially when inter-package compatibility matters. It is the right choice when you need migration guides and risk scores aggregated and ordered, not just raw changelogs.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-28T06:39:37.258Z","isFirstParty":false,"canonicalSlug":"dependency-upgrade-plan-multi-package-e8228052"}