Updates

U in the list, or:

opi --updates

opi asks the package manager (outdated --json) and, for Rust, cargo outdated --root-deps-only, and sorts the answer by semver jump: what is safe to take, and what is a major. A 0.x minor counts as breaking, in both ecosystems.

Run on opi’s own repository, piped:

opi  updates

– Dependencies — no package.json here

✓ Dependencies (rust) — everything is current

Where something is outdated, each line carries its jump — - runemark 0.8.0 → 0.8.1 [patch] — under Safe to take or A decision each.

A repository with both manifests gets two sections, Dependencies and Dependencies (rust), because “safe to take” orders within an ecosystem and not across two. In a pnpm workspace opi asks with -r, so members’ dependencies are included.

Taking the updates

In a terminal, --updates offers to apply what it found — and then runs the commit checks on what comes back. That chain — update, install, check, what is red now — is the reason the action exists.

Three lines are offered. Staying inside the declared ranges against raising them answers in bulk, each with its own count and omitted when that count is zero; neither includes a major. Decide per package lists every finding as a ticked line, majors among them — for the case the bulk lines cannot reach: one major you have read the release notes for, beside a dozen minors you have not thought about. The safe ones start ticked and the majors do not, so confirming without touching anything does what “Raise the ranges” does, and a major is only ever taken deliberately.

Raising ranges — and with it the per-package list — is offered for pnpm only, because npm has no command that keeps the range operator: npm install x@1.1.1 turns an exact 2.1.2 into ^2.1.3.

bun’s outdated prints a table rather than JSON, so opi has no list of its own there. Instead it offers Choose in bun’s own list, which opens bun update --interactive — with -r in a workspace, so members’ packages are included — and runs the commit checks once bun is done. yarn is not offered anything: Yarn Berry has no outdated at all.

opi writes nothing itself. It calls the package manager with a list of names — no package.json, no lockfile is touched by opi. Where two lockfiles disagree and no packageManager field settles it, the offer is withheld and the finding named instead. Rust’s section carries no next step, because cargo update writes the lockfile.