wvb deploy
Mark an already-uploaded bundle version as the current one that clients receive.
wvb deploy promotes a bundle version that is already on the remote to be the current version. Clients that download the bundle then receive that version. Uploading a bundle stores it on the remote but does not make it current — deploy is the step that flips the switch.
Run it after wvb upload, or pass --deploy to upload to combine both steps in one command.
Usage
wvb deploy app --version 1.2.0
wvb deploy app --version 1.2.0 --channel beta
wvb deploy # uses config / package.json defaultsThe bundle name is the positional BUNDLE argument and falls back to the resolved name from your config or package.json. The version is the --version (-V) flag — there is no positional version argument.
Options
| Option | Aliases | Default | Description |
|---|---|---|---|
BUNDLE | — | resolved from config | Bundle name to deploy. |
--version | -V | config or package.json version | Version to mark as current. |
--channel | — | — | Release channel to deploy to. |
--config | -C | config auto-discovery | Path to the config file. |
--cwd | — | process.cwd() | Working directory for resolving paths. |
The global flags --color, --log-level, and --log-verbose also apply. See the CLI overview for details.
Requirements
deploy requires remote.deployer in your config. The deployer is the component that records which version is current on the remote, so you cannot deploy to a remote without one.
The version is the --version (-V) flag, not a positional argument. If you omit it, deploy uses
the version resolved from your config or the nearest package.json.