template-kit upgrade
The `template-kit upgrade` command — its arguments, flags, exit codes and constraints.
Move the workspace onto the latest @homepages release.
Synopsis
Section titled “Synopsis”template-kit upgrade [--dry-run] [--to <version>]| Flag | Type | Default | What it does |
|---|---|---|---|
--dry-run |
boolean | false |
Print the rewrite and change nothing |
--to <version> |
string | — | Move to this exact version instead of the published latest |
Exit codes
Section titled “Exit codes”| Code | When |
|---|---|
0 |
the ranges were rewritten and installed, or the workspace was already on the target |
1 |
the install fails, or --to names a version the registry does not carry |
Constraints
Section titled “Constraints”- Rewrites every
@homepages/*range in the workspace’s package.json together. The packages ship at one version and peer each other within a major, so moving one alone is what produces an unmet peer. - A release version is stamped as a caret; a prerelease is pinned exactly.
- Writes nothing when a package overlay is active, when there is no lockfile, or when the registry cannot be read.
- Needs no terminal — it runs the same in CI, down a pipe, and in a container.
- A failed install puts package.json back the way it was.
See also
Section titled “See also”- Every command — the rest of the CLI’s surface.
- This CLI drives any kit in
^9.0.0;template-kit --versionprints the pair.