opschain templates version unlock
templates
opschain templates version unlock <project>/<code> --version <v> [--ignore-in-use]
Unlocks a template version, making its pinned revision and metadata
writable again. The server refuses the unlock while assets use the version
— the lock is what guarantees them a frozen revision — unless
--ignore-in-use overrides the refusal.
Flags
| Flag | Meaning |
|---|---|
--version <v> | The version to unlock (required). |
--ignore-in-use | Override the in-use refusal for versions that assets are pinned to. |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Unlocked — prints unlocked version <v> of <project>/<code>. |
| 1 | The template was not found, or the server refused (assets use the version and no override was passed). |
| 2 | Usage error — missing required flag, malformed address, no server target. |
Named errors
required flag(s) "version" not set— exit 2.expected <project>/<template-code>, got "<arg>"— exit 2.template "<code>" not found in project "<project>"— exit 1.
Example
opschain templates version unlock demo/web_stack --version 1.0.0 --ignore-in-use
unlocked version 1.0.0 of demo/web_stack
See also
opschain docs cli/templates-version-lock— the counterpart.opschain docs cli/templates-show— which assets use the version.