What a dependency update breaks in your code
check_upgradeCall this before or after updating a dependency: pass the package, the version you have, the version you are moving to, and the code that uses the package (a snippet, or several files by path).
Instructions
Call this before or after updating a dependency: pass the package, the version you have, the version you are moving to, and the code that uses the package (a snippet, or several files by path). Returns each use the new version breaks, with its file and line: a removed name, a keyword no longer accepted, a newly required argument, or a call that only raises, with the release that changed it and the replacement. A break is reported only when the new version fails and the old one doesn't; deprecations are warnings, and uses DepTime can't tell about are listed apart, never as breaks. One package per call; for a whole project, deptime check-upgrade reads the version changes from its lockfiles.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"package": "<package>",
"from_version": "<from_version>"
},
"name": "check_upgrade"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Python code that uses the package, read with `ast` (never run); its uses are reported at file `<code>`. | |
| files | No | Several Python files instead of, or as well as, `code`: relative path -> source. Paths name the uses in the answer. Up to 2,000,000 characters across all of them. | |
| package | Yes | PyPI distribution name, e.g. 'langchain-core'. | |
| to_version | No | The version to update to; defaults to the newest indexed release. | |
| from_version | Yes | The version the code works with now, e.g. '0.27.2'. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The git revision the versions before were read from, if any. | |
| note | No | ||
| breaks | No | Confirmed breaks across `checked`; `deptime check-upgrade` exits 1 when > 0. | |
| checked | No | ||
| project | Yes | The directory checked, as given; `<code>` for code passed to the check_upgrade tool. | |
| skipped | No | Packages added or removed: there's no upgrade to check. | |
| files_read | No | ||
| suppressed | No | Breaks and notices left out by the project's suppressions; `note` says so. | |
| not_covered | No | Changed packages DepTime doesn't index, so nothing was checked for them. | |
| files_unreadable | No | Python files that don't parse, so nothing was read from them (first 20). |