Upgrading

The toolkit

minikit upgrade --check      # is there a newer toolkit on my channel?
minikit upgrade              # fetch, move to the branch, fast-forward, then the simulator build
minikit upgrade --channel dev
minikit upgrade --rollback   # back to where the last upgrade started

Like flutter upgrade: the checkout follows a branch — main holds releases (each one a tag), dev is development — and the CLI recompiles itself on the next run because the revision changed. Local changes in the checkout stop an upgrade unless --force. A dart pub global activate install is updated by pub instead; minikit upgrade prints the command.

A project

minikit upgrade --project --dry-run   # what would change
minikit upgrade --project             # vendor the SDK again, rewrite minikit.yaml, refresh files

It replaces packages/ with the toolkit's SDK, updates toolkit, sdk.version and sdk.checksum in minikit.yaml (other settings survive), refreshes the launcher, IDE files, the manifest schema and stale skills, then runs flutter pub get. Edits inside packages/ are refused unless --force, because they would be lost — extend the SDK through its extension points instead.