Published: 2026-08-01 · End of support: 2027-02-01
Summary
QOps 2.x reaches end of support on 1 February 2027. This notice is a six-month heads-up. Until that date 2.x keeps working exactly as it does today; after it, the 2.x distribution channel is closed and no further downloads or update checks will resolve against it.
QOps 3.x is the current line and is where all development happens.
What "end of support" means
| Until 2027-02-01 | After 2027-02-01 | |
|---|---|---|
| Existing 2.x installs | keep working | keep working — nothing is deactivated |
| 2.x downloads / update checks | available | closed |
| Fixes, security updates, support | none for 2.x (see below) | none |
Nothing is remotely disabled on your machines. What ends is the channel: the frozen 2.x distribution on qops-hub is closed, so QOps-Update and fresh installations can no longer fetch 2.x.
2.x has already been frozen for over a year
The last 2.x release is 2.2.5 (published 13 May 2025). No 2.x release has been made since, and none is planned. In practice 2.x has been receiving no fixes for well over a year already — this notice formalises a state that already exists rather than changing one.
2.x also ships a PowerShell 7 build targeting .NET 7, which Microsoft itself stopped supporting in May 2024. That build cannot be kept current regardless of our own plans.
Upgrading to 3.x
The upgrade is a single command from an existing 2.x install:
QOps-Update -Force
Alternatively, download and install the latest 3.x release directly from the installation guide if the command does not work for you.
This has been verified end-to-end on a real machine: 2.2.5 → 3.0.10, on Windows PowerShell 5.1, including the new QOps Portal, which installed and started correctly.
The upgrade itself always delivers Portal — it is bundled inside the module — but Start-QOpsPortal performs a licence check and will not start if the licence is missing or expired. An upgrade performed with an expired licence leaves you on 3.x with Portal present but unable to start until the licence is renewed; it does not leave Portal uninstalled. The upgrade itself is not blocked.
Platform builds available on each line:
| Windows PowerShell 5.1 | PowerShell 7+ | Linux | |
|---|---|---|---|
| 2.x (frozen) | x64 | x64-net7.0 (.NET 7) | linux-x64 |
| 3.x (current) | x64 | x64-net8.0 (.NET 8) | linux-x64 |
Two things to know before upgrading
- Configuration format. 3.x writes repository configuration as YAML by default, where 2.x used JSON. Existing configurations are read and migrated; no manual conversion is needed.
- Downgrading is not supported. Once a repository has been used with 3.x, going back to 2.x can fail to read the configuration. Plan the upgrade as one-way.
Timeline
- 2026-08-01 — this notice published (six-month heads-up).
- 2027-02-01 — 2.x channel closed on qops-hub. 3.x remains the supported line.
Questions
Contact DatalabsUa support if you have 2.x installations that cannot be upgraded before February 2027, so we can plan around them.