Updates to the latest QOps version.
Installs the new version whether or not the licence checks out. Where the check fails, or cannot run at all, the run says which of the two happened and carries on:
QOps-Update: license check failed. License is invalid: the license has expired. The update runs anyway: QOps-Update does not require a license. Other commands do - run QOps-Activate to restore them.
Every other command still checks the licence for itself, so this changes what you can update, not what you can do.
Syntax
QOps-Update [-Beta] [-Force] [-Channel] [-VerboseLog]
Parameters meaning:
-Beta indicates that QOps should be updated to the version with current development
-Force performs an in-session hot-reload update — downloads the new version to a versioned subdirectory and loads it immediately without restarting PowerShell. No more killing PowerShell processes.
-Channel installs from a specific release channel for this run only — it does not change the machine's default. To make a channel the machine's default, use QOps-SetUpdateChannel. Accepts letters, digits, dot, dash and underscore.
-VerboseLog enables full verbose output including complete API response dumps and debug information. By default, QOps now produces concise output summaries.
QOps-Update -Force
Examples
QOps-Update
QOps-Update -Beta -Force
QOps-Update -Channel beta-3.1