Version history
QwenWorkWhich version you are actually on
The vendor keeps one build at a time. That makes the history short and the pinning instructions important.
| Version | Build date | Status | Notes |
|---|---|---|---|
| 2.1.0 | 2026-11-18 | Current | Signing, workspace switching and automation limits refined; six packages republished |
| 2.0.2 | 2026-11-12 | Superseded | Point fix after 2.0.0 — mostly stability in long sessions |
| 2.0.0 | 2026-11-09 | Superseded | The 2.x feature release: collaboration space and automation |
Why the archive is short
Only /release/latest/ is published. Older builds are not kept on the CDN, so there is no official download for 2.0.2 today even though it existed two weeks ago. This is common for cloud-connected clients: an old client talking to a new backend is a support burden the vendor would rather not carry.
Pinning a version for a lab or image
- Download on the day you build
Take the package once, and do not re-download later assuming it is the same file.
- Record three values
Version, download date, SHA-256. Two of the three are not enough to reproduce anything.
- Store the package with the record
Name the folder with the version, not with today's date — future-you searches by version.
- Re-test on upgrade
A pinned client still talks to a live backend. Before rolling forward, run one generation task end to end; version drift shows up there first.
Downgrading
There is no supported downgrade path. Installing an older package over a newer one leaves configuration written by the newer build, and the client may refuse to start or silently reset the layout. If you must go back, uninstall, clear the configuration directory, then install the older build — and accept that local history is gone.