| title | FAQ |
|---|---|
| description | How Uptide relates to Renovate and Dependabot, where your code goes, what happens without a pack, and whether anything is pushed. |
For anyone with the usual four questions before a first run.
They open the pull request that bumps the version. Uptide answers what that bump breaks in
your code (check), migrates the code on a branch (fix), and verifies the result with your
compiler and tests. The two work together: Uptide opens a pull request only when it has a
verified migration to go with the upgrade, and the Uptide Action does that on a
schedule in your own GitHub Actions.
list, check and plan send nothing of yours: package names and versions go to your npm
registry, and list names public packages to npm's advisory endpoint. Code leaves the
machine only for assisted fixes in fix, which runs them with the Claude Agent SDK and your
own ANTHROPIC_API_KEY: the findings, the code around them, files the session reads in the
temporary clone and the output of its checks. There is no account and no Uptide server. The full model: privacy.
check works the same: a generic dependency gets the same analysis, and breaking still means
the compiler, the runtime probe or the import confirmed it (concepts).
fix migrates with the agent alone, needs a provider API key, stops at --max-cost
(default $1) and opens its pull request with a note that no pack covers the package. It opens
one only for a minor or patch whose build and tests pass after the bump; a major upgrade
without a pack is reported as no pack yet and never opened.
Packs can be written by anyone (migration packs); the next ones worth writing are
in packs/queue.json.
Not unless you say so. fix works in a temporary clone and leaves you a branch and a stored
run; nothing is pushed until you run uptide pr --yes or pass fix --pr --yes. Your
checkout, git config and hooks are compared before and after and must be identical.
Your repository's own node_modules/typescript, found the way your build finds it, so the
errors and their lines are the ones tsc would print. The bundled compiler stands in only
when the repository installs none, and the coverage line
says which one judged.