Sync the self-hosting stack
This commit is contained in:
@@ -9,6 +9,23 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
|
||||
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
|
||||
cannot be published without its entry.
|
||||
|
||||
## 2026-09-25 — The licence report counts operators, and the paid plans are Business and MSP `api 0.114.0` `web 0.139.0`
|
||||
|
||||
**The licence report sends one more number.** Next to organizations, enabled users, agents and assets,
|
||||
it now carries **operators**: enabled accounts with a platform administrator role, or an OWNER, ADMIN
|
||||
or OPERATOR role in at least one organization, counted once per account. It is a count, like the
|
||||
others — no name, no address, nothing about who they are — and the
|
||||
[field table](README.md#licence-keys-and-what-your-instance-reports) lists it. A community instance reports it too.
|
||||
|
||||
**Paid licences are now Business and MSP / Service Provider, plus the Trial.** A key issued on one of
|
||||
these plans shows its name on the licence screen. Kubernetes is listed among the features a licence
|
||||
can carry. Nothing an existing key already allows changes.
|
||||
|
||||
**Reactivating a disabled account now counts, as creating one does.** On an instance at its user
|
||||
allowance, turning an account back on is refused with the same sentence as adding one. Before, an
|
||||
account could be disabled, a new one created, and the first turned back on, ending above the
|
||||
allowance.
|
||||
|
||||
## 2026-09-25 — A licensed instance can choose the managed model while it is being installed `api 0.113.0` `web 0.138.0`
|
||||
|
||||
**The install screen now asks for the licence before the model, and offers the managed model
|
||||
|
||||
Reference in New Issue
Block a user