canasta extension set-version

Pin a user extension to a specific version

Synopsis

Move a gitops-managed user extension's submodule to a specific version (branch, tag, or commit) and stage the change, ready for canasta gitops push to distribute it to every host. This replaces the raw git checkout inside the submodule that changing an extension's version otherwise requires.

Pass the release branch matching your MediaWiki version (e.g. REL1_43) rather than a development branch like master, which is the common cause of version-mismatch regressions. Only user extensions (vendored as submodules) can be pinned. A bundled extension has no per-instance submodule, so this refuses it — to use a different version, add it to your extensions/ directory, where a user copy overrides the bundled one. Pass --run-update to apply any database schema changes for the new version immediately; otherwise run canasta maintenance update afterward if the version touches the schema.

canasta extension set-version [flags] NAME

Examples

canasta extension set-version UserPageEditProtection --ref REL1_43

Arguments

Argument	Description	Default	Required	Orchestrator
`NAME`	Extension name (the extensions/<name> submodule)		✓	Both

Flags

Flag	Shorthand	Description	Default	Required	Orchestrator
`--id`	`-i`	Canasta instance ID	*		Both
`--ref`		Version to pin to: a branch, tag, or commit SHA		✓	Both
`--run-update`		Run update.php after pinning to apply DB schema changes			Both

* Defaults to the Canasta instance matching the current directory, if any.

Global flags

Flag	Shorthand	Description	Default	Required	Orchestrator
`--help`	`-h`	Show help message and exit			Both
`--verbose`	`-v`	Enable verbose output			Both