Select a tab for the core sitectl command or one of its plugins to see install and upgrade instructions.
When you install a current v1 sitectl plugin with Homebrew or Linux packages, the package manager also installs the core sitectl command.
These docs track this published release set. Generated command references cover
core sitectl and the operator plugins; sitectl-app-tmpl is the separately
versioned contributor scaffold:
Core and plugins are separately built executables, but the reviewed versions above share the v1 SDK and RPC schema. The documentation generator records each tag’s exact commit in scripts/snippet-dependencies.json. Debian, RPM, and APK packages encode each plugin’s minimum core dependency; Homebrew installs the current core formula first. If you install release binaries manually, upgrade core and every plugin you use as one tested set:
Installing a new core binary does not change the SDK and lifecycle metadata embedded in an older plugin binary. A protocol error or missing lifecycle behavior after an upgrade is an installation/version problem, not a project migration; update the plugin before changing project files.
The APT repository authenticates signed Release metadata. The RPM repository currently authenticates signed repomd.xml metadata with repo_gpgcheck=1; package payload hashes come from that signed metadata, while individual RPM signatures are not published, so gpgcheck=0 is intentional. Do not change it to gpgcheck=1 until the packages themselves are signed.
The Linux package repository is rebuilt from current release artifacts and does not preserve every older package version. A version pin is a durable rollback only while the artifact remains available. For long-lived production rollback, retain a package-repository snapshot or archive the matching GitHub release packages and checksums.txt in controlled storage.
sitectl
sitectl-drupal
sitectl-isle
Application plugins
Homebrew
You can install sitectl using Homebrew:To upgrade later:Linux Packages
Releases publish native Linux packages through the libops package repository.To upgrade later:Binary Install
You can install sitectl by either downloading or building the sitectl binary.To upgrade a binary install, select an explicit target release and verify its archive, or rebuild from an explicit reviewed tag or full commit. Keep the previous binary until the complete core/plugin set passes the checks below.Once sitectl is on your system, put the binary in a directory that is in your $PATH.Homebrew
You can install sitectl-drupal using Homebrew:Homebrew will also install sitectl as a dependency.To upgrade later:Linux Packages
Releases publish native Linux packages through the libops package repository.The package manager will also install sitectl as a dependency.To upgrade later:Binary Install
You can install sitectl-drupal by either downloading or building the sitectl-drupal binary.Use core sitectl v1.0.2 with the reviewed Drupal v1.0.0 release. A manual binary install does not resolve that dependency for you.To upgrade a binary install, select and verify an explicit core/plugin release set or rebuild from reviewed tags or full commits. Replace both binaries before validation and keep the previous set available for rollback.Once sitectl-drupal is on your system, put the binary in a directory that is in your $PATH.sitectl-isle v1.0.0 publication is complete: GitHub release assets, the Homebrew formula, and the public APT and RPM repositories are available. The public APT Packages indexes include both amd64 and arm64 packages and declare minimum dependencies on sitectl 1.0.0 and sitectl-drupal 1.0.0.
Homebrew
You can install sitectl-isle using Homebrew:Homebrew will also install sitectl and sitectl-drupal as dependencies.The current ISLE release line requires core sitectl 1.0.0 or newer and sitectl-drupal 1.0.0 or newer. Homebrew formulas are published in dependency order: core, Drupal, then ISLE.To upgrade later:Linux Packages
Releases publish native Linux packages through the libops package repository.The package manager will also install sitectl 1.0.0 or newer and sitectl-drupal 1.0.0 or newer as dependencies. Repository publication follows the same core, Drupal, then ISLE order so every dependency is available before the dependent package.To upgrade later:Binary Install
You can install sitectl-isle by either downloading or building the sitectl-isle binary.You also need core sitectl 1.0.0 or newer and sitectl-drupal 1.0.0 or newer on your system. A manual binary install does not resolve those dependencies for you.To upgrade a binary install, update core first, then Drupal, then ISLE. Replace all three binaries in your $PATH before running sitectl create list; do not leave a partially upgraded set active.Verify the complete set after installation:Install the plugin for each application template you operate. Package names and release repositories are:Homebrew
Replace sitectl-ojs with the package from the table. Homebrew installs core sitectl as a dependency. Upgrade with brew update and brew upgrade libops/homebrew/PACKAGE.Linux Packages
After configuring the LibOps package repository from the sitectl tab, install the selected plugin by package name:The package manager installs core sitectl as a dependency. Use the same package name with apt install --only-upgrade or dnf upgrade later.Binary Install
Select an explicit plugin tag from its release link, then follow Verify a manual binary install for the plugin repository. Place the verified sitectl-<app> binary in the same $PATH as a compatible, independently verified core sitectl, and verify discovery:Core discovers plugin binaries by name from $PATH; there is no separate registration file.For a manual binary installation, run both sitectl --version and sitectl-PACKAGE --version after every upgrade. Keep the previous binaries available until sitectl create list, sitectl validate, and the relevant plugin help command work with the new set. 
